Messages in this thread | | | Date | Sat, 10 Jul 2004 12:19:14 -0700 | From | Chris Wedgwood <> | Subject | Re: XFS: how to NOT null files on fsck? |
| |
On Sat, Jul 10, 2004 at 03:55:26PM -0300, Norberto Bensa wrote:
> I think we all know that. The point, why the hell does it null > files?
A decision was made somewhere this is better than showing potentially bogus or confidential data, so on log-reply some parts of files may be zeroed. I can see arguments for an againts this and clearly for a lot of people the zeroing is a real pain.
It would be nice for some people to prevent log-replay zeroing files but then something would have to be able to determine whether or not these blocks were newly allocated (and this might contain confidential data and need to be zeroed) or previously part of the file in which case we probably would like them left alone.
I don't know any of the code well enough to know how easy this is or even if I'm telling the truth :) Hopefully someone who does can speak up on this.
--cw - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |