Re: [Nfsen-discuss] Linux filesystem type choice?
Netflow visualisation and investigation tool
Brought to you by:
phaag
|
From: Ivan A. B. <iv...@li...> - 2006-07-19 09:17:48
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Peter, On 18/07/2006 14:29, Peter Haag wrote: >>> Well - that was until last night, when a kernel upgrade appeared to wipe >>> away the filesystem. I recovered the LVM (PV/VG/LV) but xfs refused to >>> see anything (even booting back to the old kernel). >>> This has seriously dented my trust in xfs, however a few of the nice >>> things about xfs were speed of file-delete/mount/unmount/create. Trying >>> to mount a newly-formatted 1.2TB filesystem under xfs takes 4s, whereas >>> it takes 45s under reiserfs (and longer under ext3 from what I remember). ext3 actually mounts in around 5s ... but it takes about 10+ mins to create the filesystem! >>> What do other people with large filesystems use? If xfs (especially if >>> using LVM) have you seen anything like this? >>> > > I don't know if this is really a XFS issue - maybe LVM causes some problems, so XFS can handle no longer the partition. I'm using XFS for years now - since we started collecting netflow, without a > single issue with XFS. However, we don't use XFS in combination with LVM. I was wondering that. I knew you used xfs (and hence expected a post by you ;) and so wonder if it's an interaction with LVM. I know LVM "screwed up" here, but I have _always_ been able to get access to the data by recreating the LVM using the backups in /etc/lvm/ (because that restores the LVM config, and there is no reason why the on-disk data has changed). It is this point that concerned me ... xfs_restore found primary and secondary superblocks but was unable to verify them. Hopefully others will respond aswell .. I'm curious :) Cheers Ivan - -- Ivan Beveridge <iv...@li...> http://www.linx.net/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEvfiXQQZN5jq7vncRAjnqAJ9drp/HpP4Ihm6blI3YbSorwH01KQCfQpvv KFROtQwwM6VQCc99qNskFco= =ig8F -----END PGP SIGNATURE----- |