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 16:32:08 -0800
Sender: linux-xfs-bounce@xxxxxxxxxxx
http://oss.sgi.com/bugzilla/show_bug.cgi?id=387


davidc@xxxxxxxxxxxxx changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




------- Additional Comments From davidc@xxxxxxxxxxxxx  2004-17-11 16:32 PDT 
-------
Well, I'm pleased it's not an XFS bug, anyway!  And I can *still* say I have
never lost a single byte using XFS! :-) :-)

Print from parted gives the wrong value after reboot, **and even after a fresh
create!**  viz:-

(parted) mkpart primary 1 -1
(parted) p
Disk geometry for /dev/sda: 0.000-2622488.000 megabytes
Disk label type: msdos
Minor    Start       End     Type      Filesystem  Flags
1          0.031 525333.742  primary   xfs

Note:
(1) parted seems to know the FS is xfs, even though I removed the original
partition and made a new label and partition (??).
(2) after this create, /proc/partitions displays   "8     1 2685425368 sda1"
which is what I expected.
(3) **I can now mount the filesystem** and see old data there even though I
never wrote anything or created a filesystem!!!!!... xfs_check now produces no
errors.
(4) After a reboot, xfs_check finds lots of errors.
(5) Go back into parted, remove partition, recreate it and presto!, all the data
is back and xfs_check is happy once more.

Hmm, sounds maybe like a parted bug?



------- 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>