Bob Friesenhahn schrieb:
On Thu, 5 Nov 2009, Steven Samuel Cole wrote:
Definitely do
zpool scrub zpool01
to see if there is any other decay.
I have done that prior to getting the status, several times actually,
tried to indicate that in my OP. IIRC, all checksums are zero after
Thank you very much for your reply! :-)
Trevor Pretty schrieb:
Steven
I had a similar problem back in 2006 when I was first playing with ZFS.
Jeff Bronwick sent me this. It may (or not) help. I'm not sure if the
number is still the inode. If it is a please let zfs-discuss know.
> I've a n
Hello,
I couldn't find a dedicated FreeBSD/ZFS mailing list, so I hope this is
the right place to ask.
I'd like some advice if I should rely on one of my ZFS pools:
[u...@host ~]$ sudo zpool clear zpool01
...
[u...@host ~]$ sudo zpool scrub zpool01
...
[u...@host ~]$ sudo zpool status -v
Uwe Laverenz schrieb:
On Sat, Jun 21, 2008 at 01:38:25PM +1200, Steven Samuel Cole wrote:
Also, the disks are SATA300, the controller supports SATA150 only; there
is a jumper on the disks that limits them to SATA150 which I removed.
Could that be relevant ?
Yes, it could be relevant
Hello,
I see an error message every time I boot my AMD64 FreeBSD 7.0 system or
when I restart smartd. These are the dmesg lines that seem relevant to
the issue (shortened for clarity):
kernel: FreeBSD 7.0-RELEASE #0: Fri Jun 6 22:06:44 NZST 2008
kernel: CPU: AMD Athlon(tm) 64 X2 Dual Core Pr
