xfs
[Top] [All Lists]

RE: Bug with 2.4.13?

To: <gcs@xxxxxx>, <linux-xfs@xxxxxxxxxxx>
Subject: RE: Bug with 2.4.13?
From: <Hristo.Grigorov@xxxxxxxxxxxx>
Date: Fri, 26 Oct 2001 10:12:37 +0300
Sender: owner-linux-xfs@xxxxxxxxxxx
Thread-index: AcFd7Zj9naRT8fU8Rqe8R2AkkD4DMw==
Thread-topic: Bug with 2.4.13?
Hmm, I got that "Input/Output" error once (2.4.13-pre2) while 
tring to remove one tree with many subdis and files. Nothing
on the XFS partition was "accessible" after that.

But luckily I immediatelly rebooted and everything went fine.
Didn't reported that problem because the kernel was compiled with
gcc3 :)

Cheers, Hristo. 

>-----Original Message-----
>From: owner-linux-xfs@xxxxxxxxxxx 
>[mailto:owner-linux-xfs@xxxxxxxxxxx]On
>Behalf Of GCS
>Sent: Friday, October 26, 2001 10:10 AM
>To: linux-xfs@xxxxxxxxxxx
>Subject: Bug with 2.4.13?
>
>
>Hi!
>
> I am using XFS with kernel 2.4.13. Yesterday I realised that 
>I can not save
>anything to my /home, which is on XFS. Even touch /home/test 
>as root said
>input/output error. umount went ok, and as I know fsck.xfs 
>does nothing,
>I tried to mount it again. I got a lot of strange messages, 
>like bad/invalid
>(?) version 0x7345435...
> After reboot the mount crashes, and if I try it again, then 
>it stucks in
>a D state. My distribution is Debian Woody. Here is a short 
>report of the
>crash:
>Null pointer dereference at virtual address 0000152
>Eip: c01a30c7 (it points to pagebuf_unlock)
>Oops: 000
>Call trace: xlog_recover_process_iunlinks+328/644
>           xlog_recover_finish+53/144
>           xfs_log_mount_finish+31/48
>           xfs_mountfs+3070/3316
>           xfs_readsb+216/240
>
>Code: 66 83 bb 6a 01 00 00 00 75 10 80 a3 50 01 00 00 f7 53 e8 7a
>
>What should I do? Any help is appreciated.
>GCS
>


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