Re: [r222277] Strange GEOM, bsdlabel and ZFS behavior

2011-06-10 Thread Andrey V. Elsukov
On 10.06.2011 10:50, Eir Nym wrote:
 messages on the start of this dmesg are for more pages of (I have see
 them for several seconds on same hardware)
 kernel config : http://eroese.org/_/_/pub/bsd/222889/GENERIC_PF

You have mixed old partitioning classes with GEOM_PART.
You should remove from the kernel at least:
options GEOM_BSD
options GEOM_MBR
options GEOM_PC98
options GEOM_VOL

-- 
WBR, Andrey V. Elsukov



signature.asc
Description: OpenPGP digital signature


Re: [r222277] Strange GEOM, bsdlabel and ZFS behavior

2011-06-10 Thread Eir Nym
2011/6/10 Andrey V. Elsukov bu7c...@yandex.ru:
 On 10.06.2011 10:50, Eir Nym wrote:
 messages on the start of this dmesg are for more pages of (I have see
 them for several seconds on same hardware)
 kernel config : http://eroese.org/_/_/pub/bsd/222889/GENERIC_PF

 You have mixed old partitioning classes with GEOM_PART.
 You should remove from the kernel at least:
 options         GEOM_BSD
 options         GEOM_MBR
 options         GEOM_PC98
 options         GEOM_VOL


This should be documented.

 --
 WBR, Andrey V. Elsukov


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: [r222277] Strange GEOM, bsdlabel and ZFS behavior

2011-06-10 Thread Eir Nym
On 10 June 2011 11:08, Eir Nym eir...@gmail.com wrote:
 2011/6/10 Andrey V. Elsukov bu7c...@yandex.ru:
 On 10.06.2011 10:50, Eir Nym wrote:
 messages on the start of this dmesg are for more pages of (I have see
 them for several seconds on same hardware)
 kernel config : http://eroese.org/_/_/pub/bsd/222889/GENERIC_PF

 You have mixed old partitioning classes with GEOM_PART.
 You should remove from the kernel at least:
 options         GEOM_BSD
 options         GEOM_MBR
 options         GEOM_PC98
 options         GEOM_VOL


 This should be documented.

[r222913] After rebuilding and reinstalling world without these
options, anything become OK as I see. Thanks for advice.


 --
 WBR, Andrey V. Elsukov



___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: [r222277] Strange GEOM, bsdlabel and ZFS behavior

2011-06-09 Thread Eir Nym
On 8 June 2011 23:12, Vladislav V. Prodan univers...@ukr.net wrote:
 08.06.2011 17:54, Eir Nym wrote:

 On 8 June 2011 16:10, Vladislav V. Prodanunivers...@ukr.net  wrote:

 08.06.2011 11:10, Eir Nym wrote:

 gpart show is work now, but not when I load zfs into memory and try to
 add zpool into.

 and when I'll boot gpart says 'GEOM: ada0s1a invalid disklabel'

 Output:
 gpart show ada0

 #gpart show ada0
 =         63  1250263665  ada0  MBR  (596G)
           63   411807627     1  freebsd  (196G)
    411807690          54        - free -  (27k)
    411807744      202752     2  !239  (99M)
    412010496      204800     3  ntfs  [active]  (100M)
    412215296   838045696     4  ntfs  (399G)
   1250260992        2736        - free -  (1.3M)
 #gpart show ada0s1
 =         0  411807627  ada0s1  BSD  (196G)
           0  402653247       1  freebsd-zfs  (192G)
   402653247    9154380       2  freebsd-swap  (4.4G)



 gpart modify -i 1 -l disk0 ada0s1
gpart: Invalid argument

after recreate ada0s1 there gpart shows 4 GEOMs with BSD partitioning
(numbers are same as above):
ada0s1
ada0s1
ada0s1c
ada0s1c


--
If I create BSD scheme with old good bsdlabel(8): (numbers are written
by hands to minimize reboot count)
#gpart delete -i 1 ada0s1
#gpart delete -i 2 ada0s1
#gpart destroy ada0s1
#bsdlabel -w ada0s1
#gpart show ada0s1
= 0 411807627 ada0s1 BSD (196G)
  0 16 -free - (8.0k) --- used by
BSDLabel data
 16 411807611 1 !0 (196G)  --- ada0s1a

and this label is correct.

I think that GEOM part create and add commands must add some gap
before partitions for any schemes and bug is here.

 and after reboot try:
 zpool create tank /dev/gpt/disk0






 --
 Vladislav V. Prodan
 VVP24-UANIC
 +380[67]4584408
 +380[99]4060508
 vla...@jabber.ru
 ___
 freebsd-current@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: [r222277] Strange GEOM, bsdlabel and ZFS behavior

2011-06-09 Thread Eir Nym
On 9 June 2011 10:45, Eir Nym eir...@gmail.com wrote:
 On 8 June 2011 23:12, Vladislav V. Prodan univers...@ukr.net wrote:
 08.06.2011 17:54, Eir Nym wrote:

 On 8 June 2011 16:10, Vladislav V. Prodanunivers...@ukr.net  wrote:

 08.06.2011 11:10, Eir Nym wrote:

 gpart show is work now, but not when I load zfs into memory and try to
 add zpool into.

 and when I'll boot gpart says 'GEOM: ada0s1a invalid disklabel'

 Output:
 gpart show ada0

 #gpart show ada0
 =         63  1250263665  ada0  MBR  (596G)
           63   411807627     1  freebsd  (196G)
    411807690          54        - free -  (27k)
    411807744      202752     2  !239  (99M)
    412010496      204800     3  ntfs  [active]  (100M)
    412215296   838045696     4  ntfs  (399G)
   1250260992        2736        - free -  (1.3M)
 #gpart show ada0s1
 =         0  411807627  ada0s1  BSD  (196G)
           0  402653247       1  freebsd-zfs  (192G)
   402653247    9154380       2  freebsd-swap  (4.4G)



 gpart modify -i 1 -l disk0 ada0s1
 gpart: Invalid argument

 after recreate ada0s1 there gpart shows 4 GEOMs with BSD partitioning
 (numbers are same as above):
 ada0s1
 ada0s1
 ada0s1c
 ada0s1c


 --
 If I create BSD scheme with old good bsdlabel(8): (numbers are written
 by hands to minimize reboot count)
 #gpart delete -i 1 ada0s1
 #gpart delete -i 2 ada0s1
 #gpart destroy ada0s1
 #bsdlabel -w ada0s1
 #gpart show ada0s1
 = 0 411807627 ada0s1 BSD (196G)
  0 16 -free - (8.0k)                                     --- used by
 BSDLabel data
  16 411807611 1 !0 (196G)                          --- ada0s1a

 and this label is correct.

 I think that GEOM part create and add commands must add some gap
 before partitions for any schemes and bug is here.


http://www.freebsd.org/cgi/query-pr.cgi?pr=157723
http://www.freebsd.org/cgi/query-pr.cgi?pr=157724

 and after reboot try:
 zpool create tank /dev/gpt/disk0






 --
 Vladislav V. Prodan
 VVP24-UANIC
 +380[67]4584408
 +380[99]4060508
 vla...@jabber.ru
 ___
 freebsd-current@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: [r222277] Strange GEOM, bsdlabel and ZFS behavior

2011-06-09 Thread Andrey V. Elsukov
On 09.06.2011 11:31, Eir Nym wrote:
 http://www.freebsd.org/cgi/query-pr.cgi?pr=157723

Can't reproduce.

 http://www.freebsd.org/cgi/query-pr.cgi?pr=157724

First of read this tread:
http://lists.freebsd.org/pipermail/freebsd-stable/2011-May/062744.html

 and after reboot try:
 zpool create tank /dev/gpt/disk0


-- 
WBR, Andrey V. Elsukov



signature.asc
Description: OpenPGP digital signature


Re: [r222277] Strange GEOM, bsdlabel and ZFS behavior

2011-06-09 Thread Eir Nym
2011/6/9 Andrey V. Elsukov a...@freebsd.org:
 On 09.06.2011 11:31, Eir Nym wrote:
 http://www.freebsd.org/cgi/query-pr.cgi?pr=157723

 Can't reproduce.
Which revision do you use?

Following link for mail is about this.


 http://www.freebsd.org/cgi/query-pr.cgi?pr=157724

 First of read this tread:
 http://lists.freebsd.org/pipermail/freebsd-stable/2011-May/062744.html

 and after reboot try:
 zpool create tank /dev/gpt/disk0


 --
 WBR, Andrey V. Elsukov



I've already compilled r222889 and will check it today.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: [r222277] Strange GEOM, bsdlabel and ZFS behavior

2011-06-09 Thread Andrey V. Elsukov
On 09.06.2011 13:32, Eir Nym wrote:
 Which revision do you use?
 
 Following link for mail is about this.
 http://www.freebsd.org/cgi/query-pr.cgi?pr=157724

 First of read this tread:
 http://lists.freebsd.org/pipermail/freebsd-stable/2011-May/062744.html

I mean that BSD scheme created with gpart(8) is not invalid.
You always can use -b start_offset when creating partitions to preserve
metadata area. Also you can use partition with zero offset for UFS.

 I've already compilled r222889 and will check it today.

I have r222733. But it is no matter, nothing was changed in this area
for 2-3 weeks.

-- 
WBR, Andrey V. Elsukov



signature.asc
Description: OpenPGP digital signature


Re: [r222277] Strange GEOM, bsdlabel and ZFS behavior

2011-06-09 Thread Eir Nym
2011/6/9 Andrey V. Elsukov bu7c...@yandex.ru:
 On 09.06.2011 13:32, Eir Nym wrote:
 Which revision do you use?

 Following link for mail is about this.
 http://www.freebsd.org/cgi/query-pr.cgi?pr=157724

 First of read this tread:
 http://lists.freebsd.org/pipermail/freebsd-stable/2011-May/062744.html

 I mean that BSD scheme created with gpart(8) is not invalid.
 You always can use -b start_offset when creating partitions to preserve
 metadata area. Also you can use partition with zero offset for UFS.

 I've already compilled r222889 and will check it today.

 I have r222733. But it is no matter, nothing was changed in this area
 for 2-3 weeks.

GEOM will say it only after reboot.
part of dmesg log:

GEOM_LABEL[1]: MSDOSFS: gzero: no FAT signature found.
ugen0.1: Intel at usbus0
uhub0: Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1 on usbus0
ugen1.1: Intel at usbus1
uhub1: Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1 on usbus1
ugen2.1: Intel at usbus2
uhub2: Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1 on usbus2
ugen3.1: Intel at usbus3
uhub3: Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1 on usbus3
ugen4.1: Intel at usbus4
uhub4: Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1 on usbus4
GEOM_LABEL[1]: MSDOSFS: gzero: no FAT signature found.
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: SAMSUNG HM641JI 2AJ10001 ATA-8 SATA 2.x device
ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 610480MB (1250263728 512 byte sectors: 16H 63S/T 16383C)
ada0: Previously was known as ad4
SMP: AP CPU #1 Launched!
Timecounter TSC frequency 1666519680 Hz quality 800
uhub0: 2 ports with 2 removable, self powered
uhub1: 2 ports with 2 removable, self powered
uhub2: 2 ports with 2 removable, self powered
uhub3: 2 ports with 2 removable, self powered
GEOM_LABEL[1]: MSDOSFS: ada0: FAT12/16 volume not valid.
GEOM_LABEL[1]: MSDOSFS: ada0s1: no FAT signature found.
GEOM_LABEL[1]: MSDOSFS: ada0s2: no FAT signature found.
GEOM_LABEL[1]: MSDOSFS: ada0s3: FAT32 volume not valid.
GEOM_LABEL[1]: Label for provider ada0s3 is ntfs/System Reserved.
GEOM_LABEL[1]: MSDOSFS: ada0s4: FAT32 volume not valid.
GEOM_LABEL[1]: MSDOSFS: ada0s1: no FAT signature found.
g_dev_taste: make_dev_p() failed (gp-name=ada0s1, error=17)
GEOM_LABEL[1]: MSDOSFS: ada0s2: no FAT signature found.
g_dev_taste: make_dev_p() failed (gp-name=ada0s2, error=17)
GEOM_LABEL[1]: MSDOSFS: ada0s3: FAT32 volume not valid.
GEOM_LABEL[1]: Label System Reserved(ntfs/System Reserved) already
exists (ada0s3).
g_dev_taste: make_dev_p() failed (gp-name=ada0s3, error=17)
GEOM_LABEL[1]: MSDOSFS: ada0s4: FAT32 volume not valid.
g_dev_taste: make_dev_p() failed (gp-name=ada0s4, error=17)
GEOM_LABEL[1]: MSDOSFS: ada0s1a: no FAT signature found.
GEOM: ada0s1a: invalid disklabel.
GEOM_LABEL[1]: MSDOSFS: ada0s1b: no FAT signature found.
GEOM_LABEL[1]: MSDOSFS: ada0s1c: no FAT signature found.
GEOM_LABEL[1]: MSDOSFS: ada0s1a: no FAT signature found.
g_dev_taste: make_dev_p() failed (gp-name=ada0s1a, error=17)
GEOM_LABEL[1]: MSDOSFS: ada0s1b: no FAT signature found.
g_dev_taste: make_dev_p() failed (gp-name=ada0s1b, error=17)
GEOM_LABEL[1]: MSDOSFS: ada0s1a: no FAT signature found.
GEOM: ada0s1a: invalid disklabel.
g_dev_taste: make_dev_p() failed (gp-name=ada0s1a, error=17)
GEOM_LABEL[1]: MSDOSFS: ada0s1b: no FAT signature found.
g_dev_taste: make_dev_p() failed (gp-name=ada0s1b, error=17)
GEOM_LABEL[1]: MSDOSFS: ada0s1c: no FAT signature found.
g_dev_taste: make_dev_p() failed (gp-name=ada0s1c, error=17)
GEOM_LABEL[1]: MSDOSFS: ada0s1a: no FAT signature found.
g_dev_taste: make_dev_p() failed (gp-name=ada0s1a, error=17)
GEOM_LABEL[1]: MSDOSFS: ada0s1b: no FAT signature found.
g_dev_taste: make_dev_p() failed (gp-name=ada0s1b, error=17)
GEOM_LABEL[1]: MSDOSFS: ada0s1ca: no FAT signature found.
GEOM_LABEL[1]: MSDOSFS: ada0s1cb: no FAT signature found.
GEOM_LABEL[1]: MSDOSFS: ada0s1aa: no FAT signature found.
GEOM_LABEL[1]: MSDOSFS: ada0s1ab: no FAT signature found.
GEOM_LABEL[1]: MSDOSFS: ada0s1ac: no FAT signature found.
GEOM_LABEL[1]: MSDOSFS: ada0s1ca: no FAT signature found.
g_dev_taste: make_dev_p() failed (gp-name=ada0s1ca, error=17)
GEOM_LABEL[1]: MSDOSFS: ada0s1cb: no FAT signature found.
g_dev_taste: make_dev_p() failed (gp-name=ada0s1cb, error=17)
GEOM_LABEL[1]: MSDOSFS: ada0s1aa: no FAT signature found.
g_dev_taste: make_dev_p() failed (gp-name=ada0s1aa, error=17)
GEOM_LABEL[1]: MSDOSFS: ada0s1ab: no FAT signature found.
g_dev_taste: make_dev_p() failed (gp-name=ada0s1ab, error=17)
GEOM_LABEL[1]: MSDOSFS: ada0s1ac: no FAT signature found.
g_dev_taste: make_dev_p() failed (gp-name=ada0s1ac, error=17)


 --
 WBR, Andrey V. Elsukov


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: [r222277] Strange GEOM, bsdlabel and ZFS behavior

2011-06-09 Thread Andrey V. Elsukov
On 09.06.2011 14:22, Eir Nym wrote:
 GEOM will say it only after reboot.
 part of dmesg log:
 
 GEOM_LABEL[1]: MSDOSFS: gzero: no FAT signature found.
 ugen0.1: Intel at usbus0
 uhub0: Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1 on usbus0
 ugen1.1: Intel at usbus1
 uhub1: Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1 on usbus1
 ugen2.1: Intel at usbus2
 uhub2: Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1 on usbus2
 ugen3.1: Intel at usbus3
 uhub3: Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1 on usbus3
 ugen4.1: Intel at usbus4
 uhub4: Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1 on usbus4
 GEOM_LABEL[1]: MSDOSFS: gzero: no FAT signature found.
 ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
 ada0: SAMSUNG HM641JI 2AJ10001 ATA-8 SATA 2.x device
 ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
 ada0: Command Queueing enabled
 ada0: 610480MB (1250263728 512 byte sectors: 16H 63S/T 16383C)
 ada0: Previously was known as ad4
 SMP: AP CPU #1 Launched!
 Timecounter TSC frequency 1666519680 Hz quality 800
 uhub0: 2 ports with 2 removable, self powered
 uhub1: 2 ports with 2 removable, self powered
 uhub2: 2 ports with 2 removable, self powered
 uhub3: 2 ports with 2 removable, self powered
 GEOM_LABEL[1]: MSDOSFS: ada0: FAT12/16 volume not valid.
 GEOM_LABEL[1]: MSDOSFS: ada0s1: no FAT signature found.
 GEOM_LABEL[1]: MSDOSFS: ada0s2: no FAT signature found.
 GEOM_LABEL[1]: MSDOSFS: ada0s3: FAT32 volume not valid.
 GEOM_LABEL[1]: Label for provider ada0s3 is ntfs/System Reserved.
 GEOM_LABEL[1]: MSDOSFS: ada0s4: FAT32 volume not valid.
 GEOM_LABEL[1]: MSDOSFS: ada0s1: no FAT signature found.
 g_dev_taste: make_dev_p() failed (gp-name=ada0s1, error=17)
 GEOM_LABEL[1]: MSDOSFS: ada0s2: no FAT signature found.
 g_dev_taste: make_dev_p() failed (gp-name=ada0s2, error=17)
 GEOM_LABEL[1]: MSDOSFS: ada0s3: FAT32 volume not valid.
 GEOM_LABEL[1]: Label System Reserved(ntfs/System Reserved) already
 exists (ada0s3).
 g_dev_taste: make_dev_p() failed (gp-name=ada0s3, error=17)
 GEOM_LABEL[1]: MSDOSFS: ada0s4: FAT32 volume not valid.
 g_dev_taste: make_dev_p() failed (gp-name=ada0s4, error=17)
 GEOM_LABEL[1]: MSDOSFS: ada0s1a: no FAT signature found.
 GEOM: ada0s1a: invalid disklabel.
 GEOM_LABEL[1]: MSDOSFS: ada0s1b: no FAT signature found.
 GEOM_LABEL[1]: MSDOSFS: ada0s1c: no FAT signature found.
 GEOM_LABEL[1]: MSDOSFS: ada0s1a: no FAT signature found.
 g_dev_taste: make_dev_p() failed (gp-name=ada0s1a, error=17)
 GEOM_LABEL[1]: MSDOSFS: ada0s1b: no FAT signature found.
 g_dev_taste: make_dev_p() failed (gp-name=ada0s1b, error=17)
 GEOM_LABEL[1]: MSDOSFS: ada0s1a: no FAT signature found.
 GEOM: ada0s1a: invalid disklabel.
 g_dev_taste: make_dev_p() failed (gp-name=ada0s1a, error=17)
 GEOM_LABEL[1]: MSDOSFS: ada0s1b: no FAT signature found.
 g_dev_taste: make_dev_p() failed (gp-name=ada0s1b, error=17)
 GEOM_LABEL[1]: MSDOSFS: ada0s1c: no FAT signature found.
 g_dev_taste: make_dev_p() failed (gp-name=ada0s1c, error=17)
 GEOM_LABEL[1]: MSDOSFS: ada0s1a: no FAT signature found.
 g_dev_taste: make_dev_p() failed (gp-name=ada0s1a, error=17)
 GEOM_LABEL[1]: MSDOSFS: ada0s1b: no FAT signature found.
 g_dev_taste: make_dev_p() failed (gp-name=ada0s1b, error=17)
 GEOM_LABEL[1]: MSDOSFS: ada0s1ca: no FAT signature found.
 GEOM_LABEL[1]: MSDOSFS: ada0s1cb: no FAT signature found.
 GEOM_LABEL[1]: MSDOSFS: ada0s1aa: no FAT signature found.
 GEOM_LABEL[1]: MSDOSFS: ada0s1ab: no FAT signature found.
 GEOM_LABEL[1]: MSDOSFS: ada0s1ac: no FAT signature found.
 GEOM_LABEL[1]: MSDOSFS: ada0s1ca: no FAT signature found.
 g_dev_taste: make_dev_p() failed (gp-name=ada0s1ca, error=17)
 GEOM_LABEL[1]: MSDOSFS: ada0s1cb: no FAT signature found.
 g_dev_taste: make_dev_p() failed (gp-name=ada0s1cb, error=17)
 GEOM_LABEL[1]: MSDOSFS: ada0s1aa: no FAT signature found.
 g_dev_taste: make_dev_p() failed (gp-name=ada0s1aa, error=17)
 GEOM_LABEL[1]: MSDOSFS: ada0s1ab: no FAT signature found.
 g_dev_taste: make_dev_p() failed (gp-name=ada0s1ab, error=17)
 GEOM_LABEL[1]: MSDOSFS: ada0s1ac: no FAT signature found.
 g_dev_taste: make_dev_p() failed (gp-name=ada0s1ac, error=17)

It is strange. I think you have something incorrect in your configuration.
Can you show output of these commands:
1. kldstat
2. cat /boot/loader.conf
3. grep GEOM /path/to/your/kernel/config

-- 
WBR, Andrey V. Elsukov



signature.asc
Description: OpenPGP digital signature


[r222277] Strange GEOM, bsdlabel and ZFS behavior

2011-06-08 Thread Eir Nym
I have FreeBSD-CURRENT r77. I try to install ZFS root into MBR
using manual on wiki page.

There is some problem with GEOM and BSD label:

# gpart create -s BSD ada0s1
# gpart add -s 192G -t freebsd-zfs ada0s1
# gpart add -t freebsd-swap ada0s1
#gpart show ada0s1
...

gpart show is work now, but not when I load zfs into memory and try to
add zpool into.

and when I'll boot gpart says 'GEOM: ada0s1a invalid disklabel'


PS: there're too much bsdlabel devices (previous releases gives much
less device nodes (there was no aa, ab, ac, ca, cb)
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: [r222277] Strange GEOM, bsdlabel and ZFS behavior

2011-06-08 Thread Vladislav V. Prodan

08.06.2011 11:10, Eir Nym wrote:

gpart show is work now, but not when I load zfs into memory and try to
add zpool into.

and when I'll boot gpart says 'GEOM: ada0s1a invalid disklabel'


Output:
gpart show ada0


--
Vladislav V. Prodan
VVP24-UANIC
+380[67]4584408
+380[99]4060508
vla...@jabber.ru
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: [r222277] Strange GEOM, bsdlabel and ZFS behavior

2011-06-08 Thread Eir Nym
On 8 June 2011 16:10, Vladislav V. Prodan univers...@ukr.net wrote:
 08.06.2011 11:10, Eir Nym wrote:

 gpart show is work now, but not when I load zfs into memory and try to
 add zpool into.

 and when I'll boot gpart says 'GEOM: ada0s1a invalid disklabel'

 Output:
 gpart show ada0

#gpart show ada0
=63  1250263665  ada0  MBR  (596G)
  63   411807627 1  freebsd  (196G)
   411807690  54- free -  (27k)
   411807744  202752 2  !239  (99M)
   412010496  204800 3  ntfs  [active]  (100M)
   412215296   838045696 4  ntfs  (399G)
  12502609922736- free -  (1.3M)
#gpart show ada0s1
=0  411807627  ada0s1  BSD  (196G)
  0  402653247   1  freebsd-zfs  (192G)
  4026532479154380   2  freebsd-swap  (4.4G)


 --
 Vladislav V. Prodan
 VVP24-UANIC
 +380[67]4584408
 +380[99]4060508
 vla...@jabber.ru
 ___
 freebsd-current@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: [r222277] Strange GEOM, bsdlabel and ZFS behavior

2011-06-08 Thread Vladislav V. Prodan

08.06.2011 17:54, Eir Nym wrote:

On 8 June 2011 16:10, Vladislav V. Prodanunivers...@ukr.net  wrote:

08.06.2011 11:10, Eir Nym wrote:


gpart show is work now, but not when I load zfs into memory and try to
add zpool into.

and when I'll boot gpart says 'GEOM: ada0s1a invalid disklabel'


Output:
gpart show ada0


#gpart show ada0
= 63  1250263665  ada0  MBR  (596G)
   63   411807627 1  freebsd  (196G)
411807690  54- free -  (27k)
411807744  202752 2  !239  (99M)
412010496  204800 3  ntfs  [active]  (100M)
412215296   838045696 4  ntfs  (399G)
   12502609922736- free -  (1.3M)
#gpart show ada0s1
= 0  411807627  ada0s1  BSD  (196G)
   0  402653247   1  freebsd-zfs  (192G)
   4026532479154380   2  freebsd-swap  (4.4G)





gpart modify -i 1 -l disk0 ada0s1
and after reboot try:
zpool create tank /dev/gpt/disk0




--
Vladislav V. Prodan
VVP24-UANIC
+380[67]4584408
+380[99]4060508
vla...@jabber.ru
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org