From: Eric Sandeen <sandeen@sandeen.net>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: file preallocation without unwritten flag being set
Date: Wed, 13 May 2009 19:41:22 -0500 [thread overview]
Message-ID: <4A0B68B2.70208@sandeen.net> (raw)
In-Reply-To: <20090514003422.GM16929@discord.disaster>
Dave Chinner wrote:
>> Unmounting will flush the filesytem address space, but not the block
>> device address space.
>
> Not exactly the problem, though. XFS opens it's own device address space
> when mounting - not the address space you get by opening /dev/sdX.
> xfs_db uses the address space associated with /dev/sdX. hence
> if you do:
>
> # xfs_db /dev/sdc
> ....
> # mount /dev/sdc
> <do some changes>
> # unmount /dev/sdc
> # xfs_db /dev/sdc
>
> The second invocation of xfs_db will not see any of the changes that
> occured to the filesystem because it will read from the buffers
> cached on /dev/sdc during the first invocation.
>
> This is the same problem Grub has....
We meant the same thing, even if I said it wrong ;)
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-05-14 0:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 23:02 file preallocation without unwritten flag being set p v
2009-05-13 0:04 ` Eric Sandeen
2009-05-13 4:34 ` p v
2009-05-13 5:08 ` Eric Sandeen
2009-05-13 21:05 ` p v
2009-05-13 21:48 ` Eric Sandeen
2009-05-13 22:28 ` Dave Chinner
2009-05-13 23:51 ` p v
2009-05-14 0:17 ` Eric Sandeen
2009-05-14 0:34 ` Dave Chinner
2009-05-14 0:41 ` Eric Sandeen [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=4A0B68B2.70208@sandeen.net \
--to=sandeen@sandeen.net \
--cc=david@fromorbit.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.