[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <9EA6C408-DC45-457F-B7FA-93F08A769E78@sun.com>
Date: Wed, 04 Nov 2009 01:05:28 -0700
From: Andreas Dilger <adilger@....com>
To: Eric Sandeen <sandeen@...hat.com>
Cc: Greg Freemyer <greg.freemyer@...il.com>,
Theodore Tso <tytso@....edu>,
Ted Augustine <taugustine@...hpathways.com>,
Alexey Fisher <bug-track@...her-privat.net>,
linux-ext4@...r.kernel.org
Subject: Re: xt4 - True Readonly mount [WAS - Re: [Bug 14354] Bad corruption
with 2.6.32-rc1 and upwards]
On 2009-11-02, at 16:02, Eric Sandeen wrote:
> Andreas Dilger wrote:
>> I thought Takashi Sato was working on allowing a filesystem freeze
>> ioctl from userspace? This would hook into the filesystem-specific
>> freeze code so that when the ioctl() returns the on-disk filesystem
>> is fully consistent and does not even require journal replay.
>
> That's in and done; most recent xfsprogs' xfs_freeze utility will
> even freeze non-xfs filesystems now :) Otherwise a wrapper utility
> around the ioctl would be trivial to write.
It probably makes sense to add a tune2fs option to freeze and unfreeze
the
filesystem? That would allow ext* users to have an available/documented
command even if they don't have xfsprogs installed.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists