Use gpart and add created partition to your raidz- for example
[code]
backupstorage# gpart create -s GPT ad0
backupstorage# gpart add -b 34 -s 1953525101 -i 1 -t freebsd-zfs -l
disk0 ad0
backupstorage# gpart show
=>34 1953525101 da0 GPT (932G)
34 19535251011 freebsd-z
On Wed, 10 Feb 2010 10:18:49 +0100 Marius Nünnerich
wrote about Re: zpool vdev vs. glabel:
MN> It seems there is some kind of race condition with zfs either picking
MN> up the disk itself or the label device for the same disk. I guess it's
MN> which ever it probes first.
This co
2010/2/10 Gerrit Kühn :
> On Tue, 9 Feb 2010 13:27:21 -0700 Elliot Finley
> wrote about Re: zpool vdev vs. glabel:
>
> EF> I ran into this same problem. you need to clean the beginning and end
> EF> of your disk off before glabeling and adding it to your pool. clean
>
On Wed, Feb 10, 2010 at 09:24:12AM +0100, Gerrit Kühn wrote:
> On Tue, 9 Feb 2010 13:27:21 -0700 Elliot Finley
> wrote about Re: zpool vdev vs. glabel:
>
> EF> I ran into this same problem. you need to clean the beginning and end
> EF> of your disk off before glabeling
On Tue, 9 Feb 2010 13:27:21 -0700 Elliot Finley
wrote about Re: zpool vdev vs. glabel:
EF> I ran into this same problem. you need to clean the beginning and end
EF> of your disk off before glabeling and adding it to your pool. clean
EF> with dd if=/dev/zero...
Hm, I think I did that
On Tue, 09 Feb 2010 18:10:21 +0100, Freddie Cash wrote:
On Tue, Feb 9, 2010 at 6:26 AM, Jeremy Chadwick
wrote:
Also, I'm a little confused as to the use of glabel in this case. In
what condition do your disk indices (e.g. X of daX) change? Are you
yanking multiple disks out of a system at
I ran into this same problem. you need to clean the beginning and end of
your disk off before glabeling and adding it to your pool. clean with dd
if=/dev/zero...
2010/2/9 Gerrit Kühn
> Hi,
>
> I have created a raidz2 with disk I labeled with glabel before. Right
> after creation this pool look
On Tue, Feb 9, 2010 at 6:26 AM, Jeremy Chadwick wrote:
> Also, I'm a little confused as to the use of glabel in this case. In
> what condition do your disk indices (e.g. X of daX) change? Are you
> yanking multiple disks out of a system at the same time and then shoving
> them back into differen
On Tue, 9 Feb 2010 06:26:58 -0800 Jeremy Chadwick
wrote about Re: zpool vdev vs. glabel:
JC> > I'm running out of ideas here...
JC> Would "zpool export" and "zpool import" be necessary in this case?
I tried that several times, does not change anything.
JC&
On Tue, Feb 09, 2010 at 03:06:06PM +0100, Gerrit Kühn wrote:
> Hi,
>
> I have created a raidz2 with disk I labeled with glabel before. Right
> after creation this pool looked fine, using devices label/tank[1-6].
>
> I did some tests with replacing/swapping disks and so on. After doing a
>
> zpoo
Hi,
I have created a raidz2 with disk I labeled with glabel before. Right
after creation this pool looked fine, using devices label/tank[1-6].
I did some tests with replacing/swapping disks and so on. After doing a
zpool offline tank label/tank6
remove disk
camcontrol rescan all
insert disk
camc
11 matches
Mail list logo
