From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: [linux-lvm] snapshots of busy ext2 file system corrupt References: <20020226095919.F12832@lynx.adilger.int> <2412370000.1014745130@tiny> From: Urs Thuermann In-Reply-To: <2412370000.1014745130@tiny>; from Chris Mason on Tue, 26 Feb 2002 12:38:50 -0500 Message-Id: Sender: linux-lvm-admin@sistina.com Errors-To: linux-lvm-admin@sistina.com Reply-To: linux-lvm@sistina.com List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: Date: Tue Feb 26 13:30:02 2002 List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-lvm@sistina.com Chris Mason writes: > For ext2, the best we could do would probably be a hack based on > locking the super. As far as I know, nobody is planning on this, :-( > especially given how easy it is to go from ext2->ext3. Some performance tests I made with ext2, ext3, and reiserfs convinced me to stay with ext2. ext3 was significantly slower than ext2 on some operations (and reiserfs even worse than that). urs