On 2016/03/09 11:32, Naohiro Aota wrote:
2016-03-07 12:05 GMT+09:00 Satoru Takeuchi :
- It's better to show a warning message for the exceptional case
that one of objectid (in most case, inode number) reaches its
highest value. Show this message only once to avoid filling
dmesg with it.
On 2016/03/09 4:24, Goffredo Baroncelli wrote:
> On 2016-03-07 04:05, Satoru Takeuchi wrote:
>> - It's better to show a warning message for the exceptional case
>> that one of objectid (in most case, inode number) reaches its
>> highest value. Show this message only once to avoid filling
>>
2016-03-07 12:05 GMT+09:00 Satoru Takeuchi :
> - It's better to show a warning message for the exceptional case
> that one of objectid (in most case, inode number) reaches its
> highest value. Show this message only once to avoid filling
> dmesg with it.
> - EOVERFLOW is more proper return va
On 2016-03-07 04:05, Satoru Takeuchi wrote:
> - It's better to show a warning message for the exceptional case
>that one of objectid (in most case, inode number) reaches its
>highest value. Show this message only once to avoid filling
>dmesg with it.
> - EOVERFLOW is more proper return
On 2016/03/07 12:05, Satoru Takeuchi wrote:
> - It's better to show a warning message for the exceptional case
>that one of objectid (in most case, inode number) reaches its
>highest value. Show this message only once to avoid filling
>dmesg with it.
> - EOVERFLOW is more proper return
- It's better to show a warning message for the exceptional case
that one of objectid (in most case, inode number) reaches its
highest value. Show this message only once to avoid filling
dmesg with it.
- EOVERFLOW is more proper return value for this case.
ENOSPC is for "No space left on de
