Hi Marc (and all the others),
Marc Bevand wrote:
> So Carsten: Mattias is right, you did not simulate a silent data corruption
> error. hdparm --make-bad-sector just introduces a regular media error that
> *any* RAID level can detect and fix.
OK, I'll need to go back to our tests performed mon
If this thing goes around FUSE, china folks could love it...
http://zfs-on-fuse.blogspot.com/
http://mlsx.xplore.cn/2008/12/18/zfs-fuse-poor-performance.html#more-1182
best,
z
- Original Message -
From: "hardware technician"
To:
Sent: Friday, January 02, 2009 12:59 AM
Subject: [zfs-di
http://translate.google.com/translate?sl=auto&tl=en&u=http%3A%2F%2Ffeeds.feedburner.com%2F~r%2FJainuxsWebLog%2F~3%2F496764318%2F
Any comments?
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://ma
Mattias Pantzare gmail.com> writes:
> On Tue, Dec 30, 2008 at 11:30, Carsten Aulbert wrote:
> > [...]
> > where we wrote data to the RAID, powered the system down, pulled out one
> > disk, inserted it into another computer and changed the sector checksum
> > of a few sectors (using hdparm's utilit
Hi!
Im running popensolaris b101 and ive made a zfs pool called tank and an fs
inside of it tank/public, ive shared it with smb.
zfs set sharesmb=on tank/public
im using solaris smb and not samba.
The problem is this. When i connect and create a file its readable to everyone
but it should be 7
