|To:||Jeff Breidenbach <jeff@xxxxxxx>|
|Subject:||Re: tuning, many small files, small blocksize|
|From:||Timothy Shimmin <tes@xxxxxxx>|
|Date:||Tue, 19 Feb 2008 11:48:53 +1100|
|Cc:||Hannes Dorbath <light@xxxxxxxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx|
|References:||<e03b90ae0802152101t2bfa4644kcca5d6329239f9ff@xxxxxxxxxxxxxx> <47B6ACC5.3030605@xxxxxxxxxxxxxxxxxxxx> <e03b90ae0802160224v600bd94exb2a1007ca7af7b65@xxxxxxxxxxxxxx>|
|User-agent:||Thunderbird 18.104.22.168 (Macintosh/20071031)|
Jeff Breidenbach wrote:
the kernel before April is painful but I'll do it if important. Presumably there's no simple way to migrate a non-lazy xfs filesytem to a lazy one.
Dave would know that answer. But on IRIX we used xfs_chver...
Using the +c option one can enable a filesystem to use lazy counters. Note that you must run xfs_repair(1M) after setting this option to build the internal state that is required to support this functionality. Using the -c option one can disable lazy counters if it is enabled. Note that you must run xfs_repair(1M) after clearing this option to ensure that the internal state of the filesystem is consistent.
On Linux we have xfs_admin (wrapper around db) and the "version" command in xfs_db. However, it looks like "version" only does: extflg, v2-logs, attr1, attr2, but not lazy sb counters. --Tim
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: Differences in mkfs.xfs and xfs_info output., David Chinner|
|Next by Date:||Re: Differences in mkfs.xfs and xfs_info output., Jan Derfinak|
|Previous by Thread:||Re: tuning, many small files, small blocksize, Jeff Breidenbach|
|Next by Thread:||Re: tuning, many small files, small blocksize, pg_xfs2|
|Indexes:||[Date] [Thread] [Top] [All Lists]|