xfs
[Top] [All Lists]

Re: synchronization of XFS

To: Stefan Smietanowski <stesmi@xxxxxxxxxx>
Subject: Re: synchronization of XFS
From: Steve Lord <lord@xxxxxxx>
Date: Thu, 25 Mar 2004 17:02:35 -0600
Cc: Christoph Hellwig <hch@xxxxxxxxxxxxx>, Chris Wedgwood <cw@xxxxxxxx>, "IKARASHI, Seiichi" <ikarashi@xxxxxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx
In-reply-to: <406361F2.6060308@stesmi.com>
References: <4060F7FC.8090602@miraclelinux.com> <20040325063902.GA9697@dingdong.cryptoapps.com> <4062C97A.6030702@miraclelinux.com> <20040325124152.GA12078@dingdong.cryptoapps.com> <4062D7E5.6070501@stesmi.com> <20040325132200.GA12333@dingdong.cryptoapps.com> <4062E19A.90207@xfs.org> <20040325140723.GA12558@dingdong.cryptoapps.com> <20040325144519.A23764@infradead.org> <40635F04.6010109@xfs.org> <40636032.3000402@stesmi.com> <4063612E.4030109@xfs.org> <406361F2.6060308@stesmi.com>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mozilla Thunderbird 0.5 (X11/20040208)
Stefan Smietanowski wrote:
> 
> Yup. That's what's happening. It first does one run with --just-copy
> where it writes the files using the filesystem then reads the same
> files using the blockdevice and it's own filesystem code basically.
> 
> // Stefan
> 

And I presume the files are missing?

The bizzare part of this is that if you read the via the block
device interface, you are looking at the same in memory pages
which xfs uses for the metadata cache. So even if the data has
not hit disk yet, things such as names in directories should
be visible in the metadata cache. Inodes may be more tricky,
since flushing of inodes into the metadata cache is delayed.

Try this for an experiment, before the run, set

/proc/sys/fs/xfs/sync_interval

down to some small number like 1000, pause for a couple
of seconds after calling sync, and then see if grub
can see the files via the block device.

This tunable controls how long xfs delays writing out
inodes into the metadata cache from their internal format.

Steve


<Prev in Thread] Current Thread [Next in Thread>