[zfs-code] ZFS disk give a kstat_create namespace collision

2008-02-08 Thread Kory Wheatley
We have a zfs pool setup as an iscsi disk attached to an equallogic box. When we boot the system up we get the following warning. WARNING: kstat_create('mdi', 0, 'ssd0.t1.iscsi0'): namespace collision I believe this is regards to the zfs iscsi disks. This may not be the right forum but I don't

[zfs-code] Design for EAs in dnode.

2008-02-08 Thread Ricardo M. Correia
nuel Correia Lustre Engineering Sun Microsystems, Inc. Portugal Phone +351.214134023 / x58723 Mobile +351.912590825 Email Ricardo.M.Correia at Sun.COM -- next part -- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-code/attachments/20080208/bd

[zfs-code] Design for EAs in dnode.

2008-02-08 Thread Andreas Dilger
On Feb 08, 2008 18:09 +, Ricardo Correia wrote: > On Qui, 2008-02-07 at 22:51 -0700, Neil Perrin wrote: > > I believe when a prototype using 1K dnodes was tested it showed an > > unacceptable (30%?) hit on some benchmarks. So if can possibly > > avoid increasing the dnode size (by default) the

[zfs-code] Design for EAs in dnode.

2008-02-08 Thread Andreas Dilger
On Feb 07, 2008 17:14 +, Ricardo Correia wrote: > On Qui, 2008-02-07 at 09:44 -0700, Mark Shellenbaum wrote: > > Section 2.2.4 > > > > Not sure what you mean by storing all xattrs in a single object? Are you > > saying all of the Lustre attributes would be stored in a single Solaris > > ext

[zfs-code] Design for EAs in dnode.

2008-02-08 Thread Matthew Ahrens
Andreas Dilger wrote: > On Feb 07, 2008 17:14 +, Ricardo Correia wrote: >> On Qui, 2008-02-07 at 09:44 -0700, Mark Shellenbaum wrote: >>> Section 2.2.4 >>> >>> Not sure what you mean by storing all xattrs in a single object? Are you >>> saying all of the Lustre attributes would be stored in a

[zfs-code] Design for EAs in dnode.

2008-02-08 Thread Matthew Ahrens
Ricardo M. Correia wrote: > On Qui, 2008-02-07 at 22:51 -0700, Neil Perrin wrote: >> I believe when a prototype using 1K dnodes was tested it showed an >> unacceptable (30%?) hit on some benchmarks. So if can possibly >> avoid increasing the dnode size (by default) then we should do so. > > Hmm, i

[zfs-code] RAIDZ(2) expansion?

2008-02-08 Thread Brandon Barker
This is pretty startling. I just assumed that something like this would work, since most people have growing data needs and adding new pools to a stripe would be a waste of money, space, power, time, etc. I'm glad I read this - I'll go ahead and buy more hard drives now, though I would rather

[zfs-code] Design for EAs in dnode.

2008-02-08 Thread Neil Perrin
Andreas Dilger wrote: > On Feb 07, 2008 22:51 -0700, Neil Perrin wrote: >>> It seems to me that the usefulness of extended attributes is to >>> efficiently store small amounts of information associated with a file, >>> and I think these would make more sense to be in the dnode (possibly >>> m

[zfs-code] Design for EAs in dnode.

2008-02-08 Thread Andreas Dilger
On Feb 07, 2008 22:51 -0700, Neil Perrin wrote: > > It seems to me that the usefulness of extended attributes is to > > efficiently store small amounts of information associated with a file, > > and I think these would make more sense to be in the dnode (possibly > > making it 1K by default) or