[GRLUG] weird mount thing

[Steve Romanow]

On 3/7/2011 10:28 AM, Michael Mol wrote:
> On Mon, Mar 7, 2011 at 10:18 AM, John-Thomas Richards<jtr at jrichards.org>  wrote:
>> I attempted to unmount something earlier and it wouldn't unmount.  When
>> I did a `mount' I received this along with the usual stuff I expect to
>> see:
>>
>> /dev/sda6 on /home type ext3 (rw,commit=0,commit=600,commit=0,commit=600,commit=0,commit=600,commit=0,commit=600,commit=0,commit=600,commit=0,commit=600,commit=0,commit=600,commit=0,commit=600,commit=0,commit=600,commit=0,commit=600,commit=0,commit=600,commit=0,commit=600,commit=0,commit=600,commit=0,commit=600,commit=0,commit=600,commit=0,commit=0,commit=0,commit=600,commit=0,commit=600,commit=0,commit=600.......
>>
>> The `commit=0,commit=600' repeats many times.  I've never seen this
>> before.  Any ideas why I'm getting this?  None of the other mount points
>> do this (well, / shows `/dev/sda5 on / type ext3
>> (rw,errors=remount-ro,commit=0)').  Should I be concerned about
>> something?
> That's clearly a bug somewhere. Even if there's a hardware issue
> somewhere, something would likely need to be screwed up in code for
> that kind of iterative listing error. You should report it to your
> distro's bugtracker for the package owning mount/umount.
>
> I'd include:
>
> * normal and 'strace' output for:
> ** mount
> ** umount /home
> * any seemingly-relevant lines in syslog in proximity to when that
> mount point was mounted, and  the same in proximity to when you
> attempted to unmount
> * The output of 'file -s /dev/sda6'.
>
> Finally, I'd try running fsck on the /dev/sda6, possibly from a
> different machine, after running smart tests on the drive, and include
> the output from those.
>
Would a livecd be sufficient so the drove and cables are not disturbed?  
I would diagnose it inplace before moving it.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.