Bug 23970 - ext3 0.0.5e appears to attempt to modify filesystem even when mounted read-only
Summary: ext3 0.0.5e appears to attempt to modify filesystem even when mounted read-only
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat High Availability Server
Classification: Retired
Component: ext3
Version: beta
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Stephen Tweedie
QA Contact: Wil Harris
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-01-14 00:47 UTC by Jay Weber
Modified: 2007-04-18 16:30 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2001-05-07 21:15:27 UTC


Attachments (Terms of Use)

Description Red Hat Bugzilla 2001-01-14 00:47:12 UTC
Using LVM snapshot integration with ext3 I've noted that even if my ext3
filesystem which was
snapshotted was in a clean state at snapshot time (no needs_recovery flag
set) when that filesystem is mounted read-only (via mounting the LVM
snapshot) it appears to still try to modify the filesystem during the mount
procedure as I get back some "Bad lvm_map in ll_rw_blk" messages from LVM.

In all, I gather nothing is truely changed, but it does generate some
debugging noise from the kernel/LVM.  Looking at the code it looks like
this could be related to an iput() of the journal or such possibly, as the
code shows that the journal is the first thing addressed and has many
checks regarding it.

Comment 1 Red Hat Bugzilla 2001-05-07 20:51:27 UTC
Is this still an open problem?

Comment 2 Red Hat Bugzilla 2001-05-07 21:15:22 UTC
The current release works without the mentioned problem.  I'm using 0.0.6b now. 
I'm closing the bug.


Note You need to log in before you can comment on or make changes to this bug.