On 28/11/06, Terence Patrick Donoghue [EMAIL PROTECTED] wrote:
Is there a difference - Yep,
'legacy' tells ZFS to refer to the /etc/vfstab file for FS mounts and
options
whereas
'none' tells ZFS not to mount the ZFS filesystem at all. Then you would
need to manually mount the ZFS using 'zfs set
On Tue, Nov 28, 2006 at 04:48:19PM +, Dick Davies wrote:
Just spotted one - is this intentional?
You can't delegate a dataset to a zone if mountpoint=legacy.
Changing it to 'none' works fine.
vera / # zfs create tank/delegated
vera / # zfs get mountpoint tank/delegated
NAME
On Tue, Nov 28, 2006 at 10:48:46PM -0500, Toby Thain wrote:
Her original configuration wasn't redundant, so she should expect
this kind of manual recovery from time to time. Seems a logical
conclusion to me? Or is this one of those once-in-a-lifetime strikes?
That's not an entirely true
I had the same thing happen to me twice on my x86 box. I installed ZFS (RaidZ)
on my enclosure with four drives and upon reboot the bios hangs upon detection
of the newly EFI'd drives. I've already RMA'd 4 drives to seagate and the new
batch was frozen as well. I was suspecting my enclosure,
On 29-Nov-06, at 8:53 AM, Brian Hechinger wrote:
On Tue, Nov 28, 2006 at 10:48:46PM -0500, Toby Thain wrote:
Her original configuration wasn't redundant, so she should expect
this kind of manual recovery from time to time. Seems a logical
conclusion to me? Or is this one of those
On 29-Nov-06, at 9:30 AM, David Elefante wrote:
I had the same thing happen to me twice on my x86 box. I installed
ZFS (RaidZ) on my enclosure with four drives and upon reboot the
bios hangs upon detection of the newly EFI'd drives. ... This
seems to me to be a serious problem.
On 11/30/06, David Elefante [EMAIL PROTECTED] wrote:
I had the same thing happen to me twice on my x86 box. I
installed ZFS (RaidZ) on my enclosure with four drives and
upon reboot the bios hangs upon detection of the newly EFI'd
drives. I've already RMA'd 4 drives to seagate and the new
batch
This is a problem since how can anyone use ZFS on a PC??? My motherboard is a
newly minted AM2 w/
all the latest firmware. I disabled boot detection on the sata channels and
it still refuses to b
oot. I had to purchase an external SATA enclosure to fix the drives. This
seems to me to be a
Hi Betsy,
Yes, part of this is a documentation problem.
I recently documented the find -inum scenario in the community version
of the admin guide. Please see page 156, (well, for next time) here:
http://opensolaris.org/os/community/zfs/docs/
We're working on the larger issue as well.
Cindy
I suspect a lack of an MBR could cause some BIOS implementations to
barf ..
Why?
Zeroed disks don't have that issue either.
What appears to be happening is more that raid controllers attempt
to interpret the data in the EFI label as the proprietary
hardware raid labels. At least, it seems
David Elefante wrote:
I had this happen on three different motherboards. So it seems that there
should be a procedure in the documentation that states if your BIOS doesn't
support EFI labels than you need to write ZFS to a partition (slice) not the
overlay, causing the BIOS to hang on
I know this isn't necessarily ZFS specific, but after I reboot I spin the
drives back
up, but nothing I do (devfsadm, disks, etc) can get them seen again until the
next reboot.
I've got some older scsi drives in an old Andataco Gigaraid enclosure which
I thought supported hot-swap, but I seem
Jim,
That is good news !! Let's us know how it goes.
Regards,
Sanjeev.
PS : I am out of office a couple of days.
Jim Hranicky wrote:
OK, spun down the drives again. Here's that output:
http://www.cise.ufl.edu/~jfh/zfs/threads
I just realized that I changed the configuration, so
13 matches
Mail list logo
