On 4/27/14, 4:20 PM, Dave Chinner wrote:
> On Fri, Apr 25, 2014 at 02:42:21PM -0500, Eric Sandeen wrote:
>> Add a heuristic to flush data to a file which looks like it's
>> going through a tmpfile/rename dance, but not fsynced.
>> I had a report of a system with many 0-length files after
>> package updates; as it turns out, the user had basically
>> done 'yum update' and punched the power button when it was
> So yum didn't run sync() on completion of the update? That seems
> rather dangerous to me - IMO system updates need to be guaranteed to
> be stable by the update mechanisms, not to leave the system state to
> chance if power fails or the system crashes immediately after an
>> Granted, the admin should not do this. Granted, the package
>> manager should ensure persistence of files it updated.
> Yes, yes it should. Problem solved without needing to touch XFS.
Right, I first suggested it 5 years or so ago for RPM. But hey, who
knows, someday maybe.
So no need to touch XFS, just every godawful userspace app out there...
Somebody should bring up the topic to wider audience, I'm sure they'll
all get fixed in short order. Wait, or did we try that already? :)
>> Ext4, however, added a heuristic like this for just this case;
>> someone who writes file.tmp, then renames over file, but
>> never issues an fsync.
> You mean like rsync does all the time for every file it copies?
Yeah, I guess rsync doesn't fsync either. ;)
>> Now, this does smack of O_PONIES, but I would hope that it's
>> fairly benign. If someone already synced the tmpfile, it's
>> a no-op.
> I'd suggest it will greatly impact rsync speed and have impact on
> the resultant filesystem layout as it guarantees interleaving of
> metadata and data on disk....
Ok, well, based on the responses thus far, sounds like a non-starter.
I'm not wedded to it, just thought I'd float the idea.
OTOH, it is an interesting juxtaposition to say the open O_TRUNC case
is worth catching, but the tempfile overwrite case is not.