| Subject: | Re: Which FileSystem do you use on your postfix server? |
|---|---|
| From: | Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx> |
| Date: | Fri, 31 Oct 2008 09:32:34 -0400 (EDT) |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <alpine.DEB.1.10.0810310810520.468@p34.internal.lan> |
| References: | <20081031121002.D94A11F3E98@spike.porcupine.org> <alpine.DEB.1.10.0810310810520.468@p34.internal.lan> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Alpine 1.10 (DEB 962 2008-03-14) |
On Fri, 31 Oct 2008, Justin Piszcz wrote:
http://oss.sgi.com/projects/xfs/faq.html#nulls Q: Why do I see binary NULLS in some files after recovery when I unplugged the power? Update: This issue has been addressed with a CVS fix on the 29th March 2007 and merged into mainline on 8th May 2007 for 2.6.22-rc1. XFS journals metadata updates, not data updates. After a crash you are supposed to get a consistent filesystem which looks like the state sometime shortly before the crash, NOT what the in memory image looked like the instant before the crash. Since XFS does not write data out immediately unless you tell it to with fsync, an O_SYNC or O_DIRECT open (the same is true of other filesystems), you are looking at an inode which was flushed out, but whose data was not. Typically you'll find that the inode is not taking any space since all it has is a size but no extents allocated (try examining the file with the xfs_bmap(8) command). |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: do_sync() and XFSQA test 182 failures...., Dave Chinner |
|---|---|
| Next by Date: | Re: Which FileSystem do you use on your postfix server?, Eric Sandeen |
| Previous by Thread: | Re: Which FileSystem do you use on your postfix server?, Justin Piszcz |
| Next by Thread: | Re: Which FileSystem do you use on your postfix server?, Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |