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

[TJ Davis]

Yes, it is saying that I had to unmount it which would not be worth my
effort because it is an active server.  I was just wondering if I could do a
passive check on it without unmounting it that way if it is bad I can
unmount it and clean it up.  The -N switch did not do the trick by the way.

-----Original Message-----
From: terry [mailto:linux at cowtown.net]
Sent: Thursday, February 27, 2003 11:31 PM
To: NTLUG Discussion List
Subject: Re: [NTLUG:Discuss] strange "No space" issue on /dev/md0


TJ Davis wrote:

>
> while we are on the subject of fsck I was going to run it on my 
> filesystem (ext3) just because I wanted to but it warned me that it 
> could seriously damage the filesystem.  is there a switch that I can 
> use to have it just do a test with no fixes or do I just have to test 
> it during the reboot?
>

Did it say that it could damage the filesystem because it was mounted at 
the time?
You're supposed to unmount the partition before running fsck,  Right?

> One reason that I am running it is because when I try to copy large 
> files (over 2 or 3 mb) using Samba it starts copying the file and then 
> tells me the file already exists at a size of 0 bytes and cannot be 
> copied.  I thought this might be a problem with the filesystem 
> although I doubt it so if there are any suggestions there I will 
> accept them gladly.  :-)
>
> -----Original Message-----
> From: Fred James [mailto:fredjame at concentric.net]
> Sent: Thursday, February 27, 2003 1:31 PM
> To: NTLUG Discussion List
> Subject: Re: [NTLUG:Discuss] strange "No space" issue on /dev/md0
>
>
> Fred James wrote:
>
> > Greg Edwards 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?
> >>>
> >>
> >> My man fsck says -a to automate repairs.
> >>
> >> fsck /backups -a
> >>
> >> Note the -a comes after the mount point.
> >>
> > Before or after - same error message about inconsistancies and run
> > manually.
> >
> Call off the "hounds" - I proclaim the filesystem "totally crapped" -
> turning this lemon into an "opportunity" to do a fresh install on RH 7.3
> (up from 7.1), and not try to cobble together a RAID out of a disk and a
> part of a disk (as the previous installer did) - I lean toward that
> "RAID" as a strong suspect in the initial problem, though it is always
> possible it was just me.
> Thanks anyway, for all your input.
>
> -- 
> find . -type f | xargs file | grep -i text | cut -f1 -d: | xargs grep 
> "..."
>
>
>
> _______________________________________________
> https://ntlug.org/mailman/listinfo/discuss
>
>------------------------------------------------------------------------
>
>_______________________________________________
>https://ntlug.org/mailman/listinfo/discuss
>  
>




_______________________________________________
https://ntlug.org/mailman/listinfo/discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://ntlug.org/pipermail/discuss/attachments/20030228/627a41ec/attachment.html