http://oss.sgi.com/bugzilla/show_bug.cgi?id=807
Summary: read-only mount attempts write on umount
Product: Linux XFS
Version: unspecified
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: normal
Priority: P2
Component: XFS kernel code
AssignedTo: xfs-masters@xxxxxxxxxxx
ReportedBy: dean@xxxxxxxxxx
this is the 2.6 version of bug 413 which was closed out 'cause it was reported
against linux 2.4 kernel.
if you use "mount -o ro" against a read-only device (i.e. losetup -r or blockdev
--setro, or a read-only snapshot, etc.) then when you umount the kernel attempts
to write the FS. it appears to only occur at umount though. here's what i see
in dmesg for the mount:
XFS mounting filesystem loop0
Ending clean XFS mount for filesystem: loop0
i.e. it's successful, but as soon as you try to umount:
xfs_force_shutdown(loop0,0x1) called from line 420 of file fs/xfs/xfs_rw.c.
Return address = 0xffffffffa02d0df2
Filesystem "loop0": I/O Error Detected. Shutting down filesystem: loop0
Please umount the filesystem, and rectify the problem(s)
Filesystem "loop0": xfs_log_force: error 5 returned.
Filesystem "loop0": xfs_log_force: error 5 returned.
xfs_force_shutdown(loop0,0x1) called from line 420 of file fs/xfs/xfs_rw.c.
Return address = 0xffffffffa02d0df2
Filesystem "loop0": xfs_log_force: error 5 returned.
Filesystem "loop0": xfs_log_force: error 5 returned.
Filesystem "loop0": xfs_log_force: error 5 returned.
Filesystem "loop0": xfs_log_force: error 5 returned.
Filesystem "loop0": xfs_log_force: error 5 returned.
errno 5 is EIO... i'm just assuming here it was a failed write, i could be
wrong.
in this case it was a "losetup -r" and for added measure i issued a "blockdev
--setro".
Linux sixlark 2.6.26.1-sixlark1 #1 SMP Sun Aug 3 02:06:35 PDT 2008 x86_64
GNU/Linux
--
Configure bugmail: http://oss.sgi.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
|