[NTLUG:Discuss] strange "No space" issue on /dev/md0

[Fred James]

terry wrote:

> Fred James wrote:
>
>> ...am running "fsck /backups" (-y not available for some reason) and 
>> I am keeping my finger on the y key.
>> ...been running for over an hour now (boring and I have to keep 
>> changing fingers)
>> ...is there a point at which I should assume it is futile, and just 
>> abort?
>>
> A portion of man fsck:
>
>       Currently,  standardized  file system-specific options are
>       somewhat in flux.  Although not guaranteed, the  following
>       options are supported by most file system checkers:
>
>       -a     Automatically  repair  the  file system without any
>              questions (use this  option  with  caution).   Note
>              that  e2fsck(8)  supports -a for backwards compati­
>              bility only.  This option is mapped to e2fsck's  -p
>              option  which  is safe to use, unlike the -a option
>              that most file system checkers support.
>
>
>
> _______________________________________________
> https://ntlug.org/mailman/listinfo/discuss
>
>
"/dev/md0: UNEXPECTED INCONSISTENCIES..." and said to run manually 
(without -a or -p)
Of course, now I have done what may be a "silly" - I aborted the fsck 
with <Ctrl-C>, and now I have it running again.   It was running for 2 
hours before I did that - should I just consider it a hopeless case, or 
is there hope?

-- 
find . -type f | xargs file | grep -i text | cut -f1 -d: | xargs grep "..."