when you say remove the device, I assume you mean simply make it unavailable
for import (I can't remove it from the vdev).
Yes, that's what I meant.
root@openindiana-01:/mnt# zpool import -d /dev/lofi
pool: ZP-8T-RZ1-01
id: 9952605666247778346
state: FAULTED
status: One or more
On Sat, Jun 16, 2012 at 08:54:05AM +0200, Stefan Ring wrote:
when you say remove the device, I assume you mean simply make it unavailable
for import (I can't remove it from the vdev).
Yes, that's what I meant.
root@openindiana-01:/mnt# zpool import -d /dev/lofi
??pool: ZP-8T-RZ1-01
I'm on openindiana 151-a4
Skickat från min Android MobilCindy Swearingen cindy.swearin...@oracle.com
skrev:Hi Hans,
Its important to identify your OS release to determine if
booting from a 4k disk is supported.
Thanks,
Cindy
On 06/15/12 06:14, Hans J Albertsson wrote:
I've got my root
Use 'dd' to replicate as much of lofi/2 as you can onto another device, and then
cable that into place?
It looks like you just need to put a functioning, working, but not correct
device, in that slot so that it will import and then you can 'zpool replace' the
new disk into the pool perhaps?
On Sat, Jun 16, 2012 at 09:09:53AM -0500, Gregg Wonderly wrote:
Use 'dd' to replicate as much of lofi/2 as you can onto another device, and
then
cable that into place?
It looks like you just need to put a functioning, working, but not correct
device, in that slot so that it will import
On Sat, Jun 16, 2012 at 09:58:40AM -0500, Gregg Wonderly wrote:
On Jun 16, 2012, at 9:49 AM, Scott Aitken wrote:
On Sat, Jun 16, 2012 at 09:09:53AM -0500, Gregg Wonderly wrote:
Use 'dd' to replicate as much of lofi/2 as you can onto another device,
and then
cable that into place?
2012-06-16 19:13, Scott Aitken wrote:
Given I am working with images, it's hard to put just anything in place of
lofi/2. ZFS scans all of the files in the directory for ZFS labels, so just
replacing lofi/2 with an empty file (for example) just means ZFS skips it,
which is the same result as
On Jun 15, 2012, at 7:37 AM, Hung-Sheng Tsao Ph.D. wrote:
by the way
when you format start with cylinder 1 donot use 0
There is no requirement for skipping cylinder 0 for root on Solaris, and there
never has been.
-- richard
--
ZFS and performance consulting
http://www.RichardElling.com
On x86 on zfs cyl 0 must be left out of zfs root pools.
Been there.
Skickat från min Android MobilRichard Elling richard.ell...@gmail.com
skrev:On Jun 15, 2012, at 7:37 AM, Hung-Sheng Tsao Ph.D. wrote:
by the way
when you format start with cylinder 1 donot use 0
There is no requirement for
On 06/16/12 12:23, Richard Elling wrote:
On Jun 15, 2012, at 7:37 AM, Hung-Sheng Tsao Ph.D. wrote:
by the way
when you format start with cylinder 1 donot use 0
There is no requirement for skipping cylinder 0 for root on Solaris, and there
never has been.
Maybe not for core Solaris, but it
On Jun 16, 2012, at 9:49 AM, Scott Aitken wrote:
On Sat, Jun 16, 2012 at 09:09:53AM -0500, Gregg Wonderly wrote:
Use 'dd' to replicate as much of lofi/2 as you can onto another device, and
then
cable that into place?
It looks like you just need to put a functioning, working, but not
On Jun 16, 2012, at 10:13 AM, Scott Aitken wrote:
On Sat, Jun 16, 2012 at 09:58:40AM -0500, Gregg Wonderly wrote:
On Jun 16, 2012, at 9:49 AM, Scott Aitken wrote:
On Sat, Jun 16, 2012 at 09:09:53AM -0500, Gregg Wonderly wrote:
Use 'dd' to replicate as much of lofi/2 as you can onto
may be so, but in all x86 installation if one choose the default or use
vbox image
s11, s11 express , oi, s10u10 all have zfs rpool disk partition start
from cyl 1
On this list I even come across some user some issues with zpool create
that use disk partition start from cyl 0.
rather be safe
I tried to use cylinder 0 for root on x86, but in the UFS days, and I
lost the vtoc on both mirrored disks.
The installer had selected cylinder 1 as the starting cylinder for the
first disk, and I thought I should be able to use cylinder 0 as well, so
for the mirror I partitioned it to start
14 matches
Mail list logo
