xfs
[Top] [All Lists]

[Bug 387] Filesystem corruption with large filesystem on FC3

To: xfs-master@xxxxxxxxxxx
Subject: [Bug 387] Filesystem corruption with large filesystem on FC3
From: bugzilla-daemon@xxxxxxxxxxx
Date: Wed, 17 Nov 2004 14:37:01 -0800
Sender: linux-xfs-bounce@xxxxxxxxxxx
http://oss.sgi.com/bugzilla/show_bug.cgi?id=387





------- Additional Comments From sandeen@xxxxxxx  2004-17-11 14:37 PDT -------
major minor  #blocks  name
   8     0 2685427712 sda
   8     1 2685425368 sda1

After the reboot (admittedly I did run a mkfs.xfs on this again...)
major minor  #blocks  name
   8     0 2685427712 sda
   8     1  537941720 sda1

Houston, we have a problem, but it's not in xfs.  Your partition has shrunk 
after a reboot!  XFS will have a hard time coping...

What happens if you tell parted to "print" before and after the reboot?  Is
it consistent with what you asked it to write to disk?

Although this isn't an xfs bug I am interested in the problem, because I/we
use large devices around here too....



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


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