After we changed the recordsize to 8k, We first used dd to move the data files around. We could see the time recovering a archive log dropped from 40mins to 4 mins. But when using iostat to check, the read io is about 8K for each read, the write IO is still 128k for each write. Then we used cp to move the data files around as someone said dd might not change the recordsize. after that, the time to recover a log file was drop from 4mins to 1/4 mins.
So it seems dd doens't change the recordsize completely, and cp does. And is there any utility that could check the recordsize of an existing file? On Fri, Dec 26, 2008 at 10:08 PM, Kees Nuyt <k.n...@zonnet.nl> wrote: > On Fri, 26 Dec 2008 18:49:41 +0800, "qihua wu" > <staywith...@gmail.com> wrote: > > >After I changed the recordsize to 8k, seems the read/write size is not > >always 8k when using zpool iostat to check. So ZFS doesn't obey the > >recordsize strictly? > > > Did you recreate the database? Existing files keep the > recordsize they were created with. > > Also, it could be "chained I/O", where consecutive, adjacent > records are handled in one I/O call. > > -- > ( Kees Nuyt > ) > c[_] > _______________________________________________ > zfs-discuss mailing list > zfs-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
