Thanks Darren,
re: "You can use ZFS on that volume, but it will have no redundancy
at the ZFS level, only at the disk level controlled by the T3."
I believe it is an older T3.
I'm using this system in a test lab, so data integrity is not too important for me. I mainly want to see what kind of performance I can get out of the zfs/T3 setup.
I do see a note on pg 31 of the zfs admin guide that recommends against this
configuration. (but saying it is possible).
So would I get any performance bump using zfs on the T3 volume?
Or am I just getting myself into shark infested waters?
Russ
Darren Dunham wrote:
My meta* commands all return:
"... there are no existing databases"
Then you're not using SVM volumes.
This is the T3 array:
[EMAIL PROTECTED]: format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
.....
2. c1t1d0 <SUN-T300-0201 cyl 34530 alt 2 hd 128 sec 128>
/[EMAIL PROTECTED],0/[EMAIL PROTECTED],700000/SUNW,[EMAIL
PROTECTED]/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0
mount:
/export2 on /dev/dsk/c1t1d0s0
read/write/setuid/devices/intr/largefiles/logging/xattr/onerror=panic/dev=1d80008
on Mon Jul 16 17:42:52 2007
That's a raw T3 volume, with UFS mounted directly.
I'm a little confused as to how the volume can be mounted and not be
recognized by the meta commands.
The T3 has an internal raid controller. I'm pretty sure the first
versions had no way to access the raw disks. You could create up to 2
luns, either R5 or some type of mirrored setup. I don't know which
versions allowed more than that.
It's not a JBOD, and you may not be able to use it as one.
You can use ZFS on that volume, but it will have no redundancy at the
ZFS level, only at the disk level controlled by the T3.
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
