https://bugzilla.kernel.org/show_bug.cgi?id=64191
Bug ID: 64191
Summary: XFS log crashed when unmount - with extremely
condition.
Product: File System
Version: 2.5
Kernel Version: 3.11.3
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: XFS
Assignee: xfs-masters@xxxxxxxxxxx
Reporter: jyhpsycho@xxxxxxxxx
Regression: No
Created attachment 113061
--> https://bugzilla.kernel.org/attachment.cgi?id=113061&action=edit
Kernel log when remount and xfs_repair output.
I tried to make XFS Filesystem with -d agcount=1 option. This setting is not
recommended, but I need this to minimize filesystem space overhead. But, when I
writes many files at once on extremely-small logsize filesystem and re-mount
it, That says "can't read superblock".
TO REPRODUCE:
1. Create image file. I used 4095MB, but same error occurs regardless of size.
It occures on physical disks, too.
2. Create XFS filesystem on image. For minimize log size, I used following
command:
# mkfs.xfs -b size=512 -d agcount=1 -i maxpct=0 -l size=927b test_xfs
3. Mount this image to any location. I used following:
# mount -o noatime,logbufs=8 test_xfs xfs_mount/
4. Extract kernel source on it. I used following:
# tar -xf linux-3.11.6.tar.xz --directory xfs_mount/
5. When extraction is completed, unmount that image as soon as possible.
6. Try to mount that image. That says:
mount: /dev/loop0: can't read superblock
I'll attach Kernel log and output of xfs_repair. Here I tested with openSUSE
13.1 RC1, but same error occurs any distribution and vanilla kernels I checked.
It occurs on 32bit x86, too.
CentOS 5, 6
Ubuntu 11.04, 11.10, 12.04, 12.10
openSUSE 11.2, 11.3, 11.4, 12.1, 12.2, 12.3
Kernel 2.6.18, 2.6.28~39, Kernel 3.0, 3.1, 3.3, 3.4
--
You are receiving this mail because:
You are the assignee for the bug.
|