<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>RE: [NTLUG:Discuss] strange "No space" issue on /dev/md0</TITLE>
</HEAD>
<BODY>
<BR>
<P><FONT SIZE=2>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?</FONT></P>
<P><FONT SIZE=2>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. :-)</FONT></P>
<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: Fred James [<A HREF="mailto:fredjame@concentric.net">mailto:fredjame@concentric.net</A>]</FONT>
<BR><FONT SIZE=2>Sent: Thursday, February 27, 2003 1:31 PM</FONT>
<BR><FONT SIZE=2>To: NTLUG Discussion List</FONT>
<BR><FONT SIZE=2>Subject: Re: [NTLUG:Discuss] strange "No space" issue on /dev/md0</FONT>
</P>
<BR>
<P><FONT SIZE=2>Fred James wrote:</FONT>
</P>
<P><FONT SIZE=2>> Greg Edwards wrote:</FONT>
<BR><FONT SIZE=2>></FONT>
<BR><FONT SIZE=2>>> Fred James wrote:</FONT>
<BR><FONT SIZE=2>>></FONT>
<BR><FONT SIZE=2>>>> ...am running "fsck /backups" (-y not available for some reason) and </FONT>
<BR><FONT SIZE=2>>>> I am keeping my finger on the y key.</FONT>
<BR><FONT SIZE=2>>>> ...been running for over an hour now (boring and I have to keep </FONT>
<BR><FONT SIZE=2>>>> changing fingers)</FONT>
<BR><FONT SIZE=2>>>> ...is there a point at which I should assume it is futile, and just </FONT>
<BR><FONT SIZE=2>>>> abort?</FONT>
<BR><FONT SIZE=2>>>></FONT>
<BR><FONT SIZE=2>>></FONT>
<BR><FONT SIZE=2>>> My man fsck says -a to automate repairs.</FONT>
<BR><FONT SIZE=2>>></FONT>
<BR><FONT SIZE=2>>> fsck /backups -a</FONT>
<BR><FONT SIZE=2>>></FONT>
<BR><FONT SIZE=2>>> Note the -a comes after the mount point.</FONT>
<BR><FONT SIZE=2>>></FONT>
<BR><FONT SIZE=2>> Before or after - same error message about inconsistancies and run </FONT>
<BR><FONT SIZE=2>> manually.</FONT>
<BR><FONT SIZE=2>></FONT>
<BR><FONT SIZE=2>Call off the "hounds" - I proclaim the filesystem "totally crapped" - </FONT>
<BR><FONT SIZE=2>turning this lemon into an "opportunity" to do a fresh install on RH 7.3 </FONT>
<BR><FONT SIZE=2>(up from 7.1), and not try to cobble together a RAID out of a disk and a </FONT>
<BR><FONT SIZE=2>part of a disk (as the previous installer did) - I lean toward that </FONT>
<BR><FONT SIZE=2>"RAID" as a strong suspect in the initial problem, though it is always </FONT>
<BR><FONT SIZE=2>possible it was just me.</FONT>
<BR><FONT SIZE=2>Thanks anyway, for all your input.</FONT>
</P>
<P><FONT SIZE=2>-- </FONT>
<BR><FONT SIZE=2>find . -type f | xargs file | grep -i text | cut -f1 -d: | xargs grep "..."</FONT>
</P>
<BR>
<BR>
<P><FONT SIZE=2>_______________________________________________</FONT>
<BR><FONT SIZE=2><A HREF="https://ntlug.org/mailman/listinfo/discuss" TARGET="_blank">https://ntlug.org/mailman/listinfo/discuss</A></FONT>
</P>
</BODY>
</HTML>