The resolution to this problem turned out to be enabling the 3Ware 9500S
"auto carving" option. This splits all partitions into 2TB chunks, which
are then presented to the OS as separate LUNs.
FreeBSD 5.4-RELEASE's driver for the 3Ware card does not support multiple
LUNs, but the new driver (Commo
Nice catch! I think you should report this to phk@ or ru@ who have been
the most active in the fdisk area :-)
- Giorgos
On 2005-07-28 16:40, dpk <[EMAIL PROTECTED]> wrote:
>
> I've remounted the disk readonly, and was still seeing the same errors.
> I've looked at the fdisk source and compared
On Fri, 29 Jul 2005, Giorgos Keramidas wrote:
> Hmmm, in multiuser mode, your root filesystem is mounted as read-write
> and it resides in da0, so GEOM will forbid opening the disk device in
> read-write mode for editing the partition table.
>
> In single user mode, devfs is still used, but your r
On Thu, 28 Jul 2005, dpk wrote:
> truss indicates that fdisk may be getting the error from somewhere else:
>
> stat("/dev/da0",0xbfbfeb30) = 0 (0x0)
> open("/dev/da0",0x2,00) ERR#1 'Operation not
> permitted'
> open("/dev/da0",0x0,027757765630)
On 2005-07-28 16:04, dpk <[EMAIL PROTECTED]> wrote:
> # df -k
> Filesystem 1K-blocksUsedAvail Capacity Mounted on
> /dev/da0s1a 35082074 1147642 31127868 4%/
> devfs 1 10 100%/dev
> procfs 4 40 100%/proc
> # fdisk
On Fri, 29 Jul 2005, Giorgos Keramidas wrote:
> It won't wipe away the table. It will just let you edit the existing
> table interactively, through a series of questions like:
>
> - Do you want to edit partition 1?
> - Do you want to edit partition 2?
> - Do you want to edit par
On 2005-07-28 15:52, dpk <[EMAIL PROTECTED]> wrote:
>On Thu, 21 Jul 2005, Giorgos Keramidas wrote:
>> Are you trying to start from scratch, or just making changes to the
>> existing table? If it's the second, then try the -u option:
>>
>> # fdisk -u /dev/da0
>>
>> This should give you a chanc
On Thu, 21 Jul 2005, Giorgos Keramidas wrote:
> Are you trying to start from scratch, or just making changes to the
> existing table? If it's the second, then try the -u option:
>
> # fdisk -u /dev/da0
>
> This should give you a chance to interactively change the partition
> table of the di
On 2005-07-20 06:47, dpk <[EMAIL PROTECTED]> wrote:
>On Wed, 20 Jul 2005, Lowell Gilbert wrote:
>> dpk <[EMAIL PROTECTED]> writes:
>> > Has anyone here had any luck whatsoever getting FreeBSD 5.4-RELEASE to use
>> > 4TB of space from a 4TB RAID array? It is apparent that there is a
>> > 1TB/slice l
On Wed, 20 Jul 2005, Lowell Gilbert wrote:
> dpk <[EMAIL PROTECTED]> writes:
>
> > Has anyone here had any luck whatsoever getting FreeBSD 5.4-RELEASE to use
> > 4TB of space from a 4TB RAID array? It is apparent that there is a
> > 1TB/slice limit, and sysinstall doesn't seem to be able to handle
dpk <[EMAIL PROTECTED]> writes:
> Has anyone here had any luck whatsoever getting FreeBSD 5.4-RELEASE to use
> 4TB of space from a 4TB RAID array? It is apparent that there is a
> 1TB/slice limit, and sysinstall doesn't seem to be able to handle creating
> more than 2 slices.
Since you're using s
Has anyone here had any luck whatsoever getting FreeBSD 5.4-RELEASE to use
4TB of space from a 4TB RAID array? It is apparent that there is a
1TB/slice limit, and sysinstall doesn't seem to be able to handle creating
more than 2 slices.
I read somewhere that people recommend using "gpt" to manage
12 matches
Mail list logo
