* sync_blockdev in xfs_flush_device_work
@ 2007-09-29 11:09 Christoph Hellwig
2007-10-02 23:23 ` David Chinner
0 siblings, 1 reply; 2+ messages in thread
From: Christoph Hellwig @ 2007-09-29 11:09 UTC (permalink / raw)
To: xfs
How is the sync_blockdev in the ENOSP path going to help it? It only
syncs the block device mapping which XFS doesn't use it at all.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: sync_blockdev in xfs_flush_device_work
2007-09-29 11:09 sync_blockdev in xfs_flush_device_work Christoph Hellwig
@ 2007-10-02 23:23 ` David Chinner
0 siblings, 0 replies; 2+ messages in thread
From: David Chinner @ 2007-10-02 23:23 UTC (permalink / raw)
To: Christoph Hellwig; +Cc: xfs
On Sat, Sep 29, 2007 at 01:09:21PM +0200, Christoph Hellwig wrote:
> How is the sync_blockdev in the ENOSP path going to help it? It only
> syncs the block device mapping which XFS doesn't use it at all.
Not really sure - it's probably a left over from when XFs was
using it, but still that makes no difference to ENOSPC flushing..
I think we can kill it...
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-10-02 23:23 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-09-29 11:09 sync_blockdev in xfs_flush_device_work Christoph Hellwig
2007-10-02 23:23 ` David Chinner
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox