On 2012-12-14 17:03, Edward Ned Harvey
(opensolarisisdeadlongliveopensolaris) wrote:
Suspicion and conjecture only: I think format uses a fdisk label, which has a
2T limit.
Technically, fdisk is a program and labels (partitioning tables)
are MBR and EFI/GPT :)
And fdisk at least in
Here it is:
# pstack core.format1
core 'core.format1' of 3351: format
- lwp# 1 / thread# 1
0806de73 can_efi_disk_be_expanded (0, 1, 0, ) + 7
08066a0e init_globals (8778708, 0, f416c338, 8068a38) + 4c2
08068a41 c_disk (4, 806f250, 0, 0, 0, 0)
From: zfs-discuss-boun...@opensolaris.org [mailto:zfs-discuss-
boun...@opensolaris.org] On Behalf Of sol
I added a 3TB Seagate disk (ST3000DM001) and ran the 'format' command but
it crashed and dumped core.
However the zpool 'create' command managed to create a pool on the whole
disk
Hey Sol,
Can you send me the core file, please?
I would like to file a bug for this problem.
Thanks, Cindy
On 12/14/12 02:21, sol wrote:
Here it is:
# pstack core.format1
core 'core.format1' of 3351: format
- lwp# 1 / thread# 1
0806de73
Hi
I added a 3TB Seagate disk (ST3000DM001) and ran the 'format' command but it
crashed and dumped core.
However the zpool 'create' command managed to create a pool on the whole disk
(2.68 TB space).
I hope that's only a problem with the format command and not with zfs or any
other part of
# pstack core
John
groenv...@acm.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
