xfs
[Top] [All Lists]

Re: LVM and XFS problems - xfs_force_shutdown

To: Chris Wedgwood <cw@xxxxxxxx>
Subject: Re: LVM and XFS problems - xfs_force_shutdown
From: Joshua Schmidlkofer <kernel@xxxxxxxxxxxxxx>
Date: Mon, 28 Jun 2004 15:29:31 -0700
Cc: Tom Shaw <tommy2irc@xxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx
In-reply-to: <20040627222538.GA22000@xxxxxxxxxxxxxxxxxxxxx>
References: <BAY15-DAV15qF7JyJuO0008a73b@xxxxxxxxxxx> <20040627222538.GA22000@xxxxxxxxxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mozilla Thunderbird 0.5 (X11/20040413)
Chris Wedgwood wrote:
On Sun, Jun 27, 2004 at 05:56:10PM +0100, Tom Shaw wrote:


Jun 24 00:03:46 digit kernel:  I/O error: dev 08:30, sector 47436960


That's coming from the SCSI code (__scsi_end_request).

8:30 could be /dev/sdb14 which sounds a bit unusual, maybe it aliases
to something else too?


Jun 24 00:03:46 digit kernel: I/O error in filesystem ("lvm(58,0)")
meta-data dev lvm(58,0) block 0x3ca5d320 ("xfs_trans_read_buf")
error 5 buf count 4096


XFS, error message because it the error above handed to it.  At this
point XFS can't really cope with things and you'll loose access to the
filesystem to prevent further problems.


I have done a badblocks read-write test on all of the drives and
nothing shows up, so the drives are not at fault as far as I can
tell.


Do the errors occur at the same place or different places?  If the
latter and badblocks shows clean then it might be sporadic corruption
(bad cables, power supply, the 500 tons of yellow cakes stored in your
basement, etc).


One small note here...what is 8:30??  I have looked in
/proc/partitions but it is not listed, nor can I find it in my
linux-2.4.26/Documentation/devices.txt.


Check the device files:

cw@pain:~$ ls -l /dev/sd*|grep "^b.*8, .*30"
brw-rw----    1 root     disk       8,  30 Mar 14  2002 /dev/sdb14

Does that sound reasonable?  Do you even have such a device/parition?



  --cw



Is there any chance of fixing this so that all the numbers see are consistent? Is it insane to ask? The same problems exists with iptables vs. iproute2. iptables takes it in decimal, and iproute2 takes it in hex. Those are config tools, and I can take that up with the authors, but what about this?


js


<Prev in Thread] Current Thread [Next in Thread>