Hello lists, [Please CC all answers from linux-xfs to me, since I'm not subscribed on that list] Yesterday I encountered an on-the-fly corruption of my /home filesystem. It worked perfectly one secon
Hello lists, [resend with correct email address for LKML] [Please CC all answers from linux-xfs to me, since I'm not subscribed on that list] Yesterday I encountered an on-the-fly corruption of my /h
The trigger was a bad magic number related to directories... hard to say what happened in the first place. Can you send the output from xfs_repair, that might offer some hints. Thanks, -Eric
Sorry, but as a repair was very urgent, I didn't really think of saving the xfs_repair output.. My bad I guess. Jan -- The seven year itch comes from fooling around during the fourth, fifth, and sixt
William Lee Irwin III wrote: On Mon, Nov 22, 2004 at 03:30:29PM +0100, Jan De Luyck wrote: [resend with correct email address for LKML] [Please CC all answers from linux-xfs to me, since I'm not subs
Lee Revell schrieb: On Tue, 2004-11-23 at 11:13 +0100, Prakash K. Cheemplavam wrote: Is xfs known to be broken while preempt is on? (Esp using ck's preemp big kernel lock?) Minor nitpick: Ingo wrote
Nope. This looks like your driver passed an error back up to the filesystem while it was doing metadata IO and XFS chose to shut it down to prevent further damage. It's unlikely to be a preempt/xfs p
Nathan Scott schrieb: On Tue, Nov 23, 2004 at 11:13:18AM +0100, Prakash K. Cheemplavam wrote: using ck's preemp big kernel lock?) I got following using a raid0 setup with xfs. I thought it would be a
Prakash K. Cheemplavam wrote: Nathan Scott schrieb: Did you see any of those device errors since switching to ext3? No. That's why I am wondering. I read about such errors like I got before in lkml a
Eric Sandeen schrieb: Prakash K. Cheemplavam wrote: Nathan Scott schrieb: Did you see any of those device errors since switching to ext3? No. That's why I am wondering. I read about such errors like
Hello lists, [Please CC all answers from linux-xfs to me, since I'm not subscribed on that list] Yesterday I encountered an on-the-fly corruption of my /home filesystem. It worked perfectly one secon
Hello lists, [resend with correct email address for LKML] [Please CC all answers from linux-xfs to me, since I'm not subscribed on that list] Yesterday I encountered an on-the-fly corruption of my /h
The trigger was a bad magic number related to directories... hard to say what happened in the first place. Can you send the output from xfs_repair, that might offer some hints. Thanks, -Eric
Sorry, but as a repair was very urgent, I didn't really think of saving the xfs_repair output.. My bad I guess. Jan -- The seven year itch comes from fooling around during the fourth, fifth, and sixt
William Lee Irwin III wrote: On Mon, Nov 22, 2004 at 03:30:29PM +0100, Jan De Luyck wrote: [resend with correct email address for LKML] [Please CC all answers from linux-xfs to me, since I'm not subs
Lee Revell schrieb: On Tue, 2004-11-23 at 11:13 +0100, Prakash K. Cheemplavam wrote: Is xfs known to be broken while preempt is on? (Esp using ck's preemp big kernel lock?) Minor nitpick: Ingo wrote