[zfs-discuss] zpool iostat : This command can be tricky ...

2007-04-15 Thread Dennis Clarke
I really need to take a longer look here. /* * zpool iostat [-v] [pool] ... [interval [count]] * * -v Display statistics for individual vdevs * * This command can be tricky because we want to be able to deal with pool . . . I think I may need to deal with a raw option here ?

[zfs-discuss] modify zpool_main.c for raw iostat data

2007-04-15 Thread Dennis Clarke
WARNING : long and verbose .. sorry. ALL : While doing various performance tests and measurements of IO rates with a zpool I found that the output from zpool iostat poolname was not really ready for plotting by gnuplot. The output from zpool iostat poolname looks like so : # zpool iost

Re: [zfs-discuss] Bitrot and panics

2007-04-15 Thread Eric Schrock
On Sun, Apr 15, 2007 at 01:02:23AM -0700, Andrew wrote: > IIRC, uncorrectable bitrot even in a nonessential file detected by ZFS > used to cause a kernel panic. Bug ID 4924238 was closed with the > claim that bitrot-induced panics is not a bug, but the description did > mention an open bug ID 4879

Re: [zfs-discuss] FreeBSD's system flags.

2007-04-15 Thread Manoj Joseph
Pawel Jakub Dawidek wrote: ... The other problem is that there is no spare room in ZIL structures, ie. I can't add anything to lr_setattr_t, which won't break on-disk compatibility. The suggested way of moving pools is to export it, move to antoher box and import it. Once pool is exported there s

[zfs-discuss] Bitrot and panics

2007-04-15 Thread Andrew
IIRC, uncorrectable bitrot even in a nonessential file detected by ZFS used to cause a kernel panic. Bug ID 4924238 was closed with the claim that bitrot-induced panics is not a bug, but the description did mention an open bug ID 4879357, which suggests that it's considered a bug after all. Can