From: Michael Prokop <mika@grml.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: xfs tries to write on readonly device on unmount
Date: Wed, 22 Jul 2009 13:27:25 +0200 [thread overview]
Message-ID: <2009-07-22T13-22-51@devnull.michael-prokop.at> (raw)
In-Reply-To: <20090721111909.GA29399@infradead.org>
[-- Attachment #1.1: Type: text/plain, Size: 1140 bytes --]
* Christoph Hellwig <hch@infradead.org> [20090721 13:19]:
> On Tue, Jul 21, 2009 at 12:51:20PM +0200, Michael Prokop wrote:
> > This issue might be related to
> > http://oss.sgi.com/bugzilla/show_bug.cgi?id=413
> > A XFS partition is set to read-only mode (using 'blockdev --setro')
> > and mounted. As soon as I *un*mount the filesystem there seem to
> > happen write requests.
> > I've a Tableau Forensic Bridge? which avoids the write requests and
> > attached it to a Linux live-system running kernel 2.6.28 inside
> > VMware and Virtualbox. I can easily reproduce the problem.
> Block 0 is the superblock, so it appears like there is a superblock
> write somewhere not guarded by an read-only check. Can you still
> reproduce this with a current kernel? We now do have a testcase in
> xfsqa (test 200) that checks exactly that scenario, but it doesn't
> show issues on recent kernels.
I reran the test procedure with kernel 2.6.31-rc3 and could not
reproduce the issue.
Thanks.
regards,
-mika-
--
http://michael-prokop.at/ || http://adminzen.org/
http://grml-solutions.com/ || http://grml.org/
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-07-22 11:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 10:51 xfs tries to write on readonly device on unmount Michael Prokop
2009-07-21 11:19 ` Christoph Hellwig
2009-07-22 11:27 ` Michael Prokop [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2009-07-22T13-22-51@devnull.michael-prokop.at \
--to=mika@grml.org \
--cc=hch@infradead.org \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox