Filesystems >1TB not possible on 6.0-R (anymore?).

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Filesystems >1TB not possible on 6.0-R (anymore?).

Barkley Vowk
I've got a 3TB (7 x 500GB w/ hot-spare) array on an areca board in amd64.

Under 5.4-R I could have >1TB filesystems without an issue. I recall not
having problems with 6.0-BETA5 too.

However, 6.0-R gives me a tragic:

/dev/da0s1d    723G     54G    611G     8%    /home

Certainly not what I was hoping for.

I've tried both i386 and amd64 releases.

Especially since that apparent limit is much smaller than 1TB.

Dmesg Below.

Copyright (c) 1992-2005 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
  The Regents of the University of California. All rights reserved.
FreeBSD 6.0-RELEASE #0: Wed Nov  9 09:53:34 MST 2005
     [hidden email]:/usr/obj/usr/src/sys/SMP
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Opteron(tm) Processor 252 (2591.71-MHz K8-class CPU)
   Origin = "AuthenticAMD"  Id = 0x20f51  Stepping = 1
   Features=0x78bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2>
   Features2=0x1<SSE3>
   AMD Features=0xe2500800<SYSCALL,NX,MMX+,<b25>,LM,3DNow+,3DNow>
real memory  = 4227792896 (4031 MB)
avail memory = 4082405376 (3893 MB)
ACPI APIC Table: <A M I  OEMAPIC >
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
  cpu0 (BSP): APIC ID:  0
  cpu1 (AP): APIC ID:  1
MADT: Forcing active-low polarity and level trigger for SCI
ioapic0 <Version 1.1> irqs 0-23 on motherboard
ioapic1 <Version 1.1> irqs 24-27 on motherboard
ioapic2 <Version 1.1> irqs 28-31 on motherboard
acpi0: <A M I OEMXSDT> on motherboard
acpi0: Power Button (fixed)
pci_link0: <ACPI PCI Link LNKA> irq 5 on acpi0
pci_link1: <ACPI PCI Link LNKB> irq 9 on acpi0
pci_link2: <ACPI PCI Link LNKC> irq 11 on acpi0
pci_link3: <ACPI PCI Link LNKD> irq 10 on acpi0
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
cpu0: <ACPI CPU> on acpi0
acpi_throttle0: <ACPI CPU Throttling> on cpu0
cpu1: <ACPI CPU> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> at device 6.0 on pci0
pci4: <ACPI PCI bus> on pcib1
ohci0: <OHCI (generic) USB controller> mem 0xfeafc000-0xfeafcfff irq 19 at device 0.0 on pci4
ohci0: [GIANT-LOCKED]
usb0: OHCI version 1.0, legacy support
usb0: <OHCI (generic) USB controller> on ohci0
usb0: USB revision 1.0
uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 3 ports with 3 removable, self powered
ohci1: <OHCI (generic) USB controller> mem 0xfeafd000-0xfeafdfff irq 19 at device 0.1 on pci4
ohci1: [GIANT-LOCKED]
usb1: OHCI version 1.0, legacy support
usb1: <OHCI (generic) USB controller> on ohci1
usb1: USB revision 1.0
uhub1: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 3 ports with 3 removable, self powered
atapci0: <SiI 3114 SATA150 controller> port 0xbc00-0xbc07,0xb880-0xb883,0xb800-0xb807,0xac00-0xac03,0xa880-0xa88f mem 0xfeafec00-0xfeafefff irq 19 at device 5.0 on pci4
ata2: <ATA channel 0> on atapci0
ata3: <ATA channel 1> on atapci0
ata4: <ATA channel 2> on atapci0
ata5: <ATA channel 3> on atapci0
pci4: <display, VGA> at device 6.0 (no driver attached)
fxp0: <Intel 82551 Pro/100 Ethernet> port 0xa800-0xa83f mem 0xfeafb000-0xfeafbfff,0xfeaa0000-0xfeabffff irq 18 at device 8.0 on pci4
miibus0: <MII bus> on fxp0
inphy0: <i82555 10/100 media interface> on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp0: Ethernet address: 00:e0:81:30:9d:92
isab0: <PCI-ISA bridge> at device 7.0 on pci0
isa0: <ISA bus> on isab0
atapci1: <AMD 8111 UDMA133 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 7.1 on pci0
ata0: <ATA channel 0> on atapci1
ata1: <ATA channel 1> on atapci1
pci0: <serial bus, SMBus> at device 7.2 (no driver attached)
pci0: <bridge> at device 7.3 (no driver attached)
pcib2: <ACPI PCI-PCI bridge> at device 10.0 on pci0
pci3: <ACPI PCI bus> on pcib2
bge0: <Broadcom BCM5704C Dual Gigabit Ethernet, ASIC rev. 0x2003> mem 0xfc8c0000-0xfc8cffff,0xfc8b0000-0xfc8bffff irq 24 at device 9.0 on pci3
miibus1: <MII bus> on bge0
brgphy0: <BCM5704 10/100/1000baseTX PHY> on miibus1
brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto
bge0: Ethernet address: 00:e0:81:30:9d:a4
bge1: <Broadcom BCM5704C Dual Gigabit Ethernet, ASIC rev. 0x2003> mem 0xfc8f0000-0xfc8fffff,0xfc8e0000-0xfc8effff irq 25 at device 9.1 on pci3
miibus2: <MII bus> on bge1
brgphy1: <BCM5704 10/100/1000baseTX PHY> on miibus2
brgphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto
bge1: Ethernet address: 00:e0:81:30:9d:a5
pci0: <base peripheral, interrupt controller> at device 10.1 (no driver attached)
pcib3: <ACPI PCI-PCI bridge> at device 11.0 on pci0
pci1: <ACPI PCI bus> on pcib3
pcib4: <PCI-PCI bridge> at device 1.0 on pci1
pci2: <PCI bus> on pcib4
arcmsr0: <ARECA ARC1120 PCI-X 8 PORTS SATA RAID CONTROLLER (RAID6-ENGINE Inside)
Driver Version 1.20.00.02> mem 0xfc7ff000-0xfc7fffff irq 31 at device 14.0 on pci2
arcmsr0: [GIANT-LOCKED]
pci0: <base peripheral, interrupt controller> at device 11.1 (no driver attached)
acpi_button0: <Power Button> on acpi0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A
sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
fdc0: <floppy drive controller (FDE)> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
fdc0: [FAST]
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
ppc0: <Standard parallel printer port> port 0x378-0x37f irq 7 on acpi0
ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode
ppbus0: <Parallel port bus> on ppc0
plip0: <PLIP network interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
orm0: <ISA Option ROMs> at iomem 0xc0000-0xc7fff,0xc8000-0xcc7ff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Timecounters tick every 1.000 msec
Waiting 5 seconds for SCSI devices to settle
acd0: CDROM <GCR-8523B/1.03> at ata1-master PIO4
ad4: 152627MB <Seagate ST3160827AS 3.42> at ata2-master SATA150
da0 at arcmsr0 bus 0 target 0 lun 0
da0: <Areca ARC-1120-VOL#00 R001> Fixed Direct Access SCSI-3 device
da0: 166.666MB/s transfers (83.333MHz, offset 32, 16bit), Tagged Queueing Enabled
da0: 2861638MB (5860635648 512 byte sectors: 255H 63S/T 364807C)
ar0: WARNING - mirror protection lost. RAID1 array in DEGRADED mode
ar0: 152626MB <Silicon Image Medley RAID1> status: DEGRADED
ar0: disk0 READY (master) using ad4 at ata2-master
ar0: disk1 DOWN no device found for this subdisk
SMP: AP CPU #1 Launched!
Trying to mount root from ufs:/dev/ad4s1a
bge0: link state changed to UP
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Filesystems >1TB not possible on 6.0-R (anymore?).

David Kirchner
On 11/9/05, Barkley Vowk <[hidden email]> wrote:

> I've got a 3TB (7 x 500GB w/ hot-spare) array on an areca board in amd64.
>
> Under 5.4-R I could have >1TB filesystems without an issue. I recall not
> having problems with 6.0-BETA5 too.
>
> However, 6.0-R gives me a tragic:
>
> /dev/da0s1d    723G     54G    611G     8%    /home
>
> Certainly not what I was hoping for.
>
> I've tried both i386 and amd64 releases.
>
> Especially since that apparent limit is much smaller than 1TB.

Curious. Is there any remaining space for a second slice, as in da0s2?
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Filesystems >1TB not possible on 6.0-R (anymore?).

Barkley Vowk
No. The installer showed only one slice da0s1d, and the whole disk was
assigned to it.

I'd check on the running box but:
koth# disklabel -e /dev/da0
disklabel: disks with more than 2^32-1 sectors are not supported

/dev only shows:
koth# ls /dev/da0*
/dev/da0        /dev/da0s1      /dev/da0s1c     /dev/da0s1d

So I expect it is all assigned to the one slice.

On Wed, 9 Nov 2005, David Kirchner wrote:

> On 11/9/05, Barkley Vowk <[hidden email]> wrote:
>> I've got a 3TB (7 x 500GB w/ hot-spare) array on an areca board in amd64.
>>
>> Under 5.4-R I could have >1TB filesystems without an issue. I recall not
>> having problems with 6.0-BETA5 too.
>>
>> However, 6.0-R gives me a tragic:
>>
>> /dev/da0s1d    723G     54G    611G     8%    /home
>>
>> Certainly not what I was hoping for.
>>
>> I've tried both i386 and amd64 releases.
>>
>> Especially since that apparent limit is much smaller than 1TB.
>
> Curious. Is there any remaining space for a second slice, as in da0s2?
>
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Filesystems >1TB not possible on 6.0-R (anymore?).

David Kirchner
On 11/9/05, Barkley Vowk <[hidden email]> wrote:

> No. The installer showed only one slice da0s1d, and the whole disk was
> assigned to it.
>
> I'd check on the running box but:
> koth# disklabel -e /dev/da0
> disklabel: disks with more than 2^32-1 sectors are not supported
>
> /dev only shows:
> koth# ls /dev/da0*
> /dev/da0        /dev/da0s1      /dev/da0s1c     /dev/da0s1d
>
> So I expect it is all assigned to the one slice.

Yeah, I would guess that as well.

FWIW, we've used FreeBSD 5.4 with >1TB partitions, and 5.4-STABLE as
of a few months ago. This was with a 3ware card. If something happened
to reduce the maximum slice size, it was recent.
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Filesystems >1TB not possible on 6.0-R (anymore?).

Sergey N. Voronkov
In reply to this post by Barkley Vowk
On Wed, Nov 09, 2005 at 01:09:50PM -0700, Barkley Vowk wrote:
> No. The installer showed only one slice da0s1d, and the whole disk was
> assigned to it.
>
> I'd check on the running box but:
> koth# disklabel -e /dev/da0
> disklabel: disks with more than 2^32-1 sectors are not supported

Exactly from "man disklabel":

     Due to the use of an u_int32_t to store the number of sectors, BSD labels  
     are restricted to a maximum of 2^32-1 sectors.  This usually means 2TB of  
     disk space.  Larger disks should be partitioned using another method such  
     as gpt(8).  The various BSDs all use slightly different versions of BSD    
     labels and are not generally compatible.                                  

(I havn't use it, so ask someone other...)

Serg N. Voronkov,
Sibitex Ltd.
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Filesystems >1TB not possible on 6.0-R (anymore?).

Xin LI-5
In reply to this post by Barkley Vowk
On 11/9/05, Barkley Vowk <[hidden email]> wrote:
> I've got a 3TB (7 x 500GB w/ hot-spare) array on an areca board in amd64.
>
> Under 5.4-R I could have >1TB filesystems without an issue. I recall not
> having problems with 6.0-BETA5 too.
[snip]

Would you please consider to try "gpt" instead of "bsdlabel"?

BTW.  The dmesg meesage indicates that your array is degraded :-(

Cheers,

_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Filesystems >1TB not possible on 6.0-R (anymore?).

David Kirchner
On 11/10/05, Xin LI <[hidden email]> wrote:
> Would you please consider to try "gpt" instead of "bsdlabel"?
>
> BTW.  The dmesg meesage indicates that your array is degraded :-(

Is it possible to have sysinstall use gpt instead of bsdlabel, and
then to boot from a gpt based array? I haven't had luck with it, but
maybe that was fixed with 6.0.
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Filesystems >1TB not possible on 6.0-R (anymore?).

Xin LI-5
On 11/11/05, David Kirchner <[hidden email]> wrote:
> On 11/10/05, Xin LI <[hidden email]> wrote:
> > Would you please consider to try "gpt" instead of "bsdlabel"?
> >
> > BTW.  The dmesg meesage indicates that your array is degraded :-(
>
> Is it possible to have sysinstall use gpt instead of bsdlabel, and
> then to boot from a gpt based array? I haven't had luck with it, but
> maybe that was fixed with 6.0.

I'm not quite sure, but the live system shell provided by the
installation CD (disc1) might help.

--
Xin LI <[hidden email]> http://www.delphij.net

_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[hidden email]"
Reply | Threaded
Open this post in threaded view
|

Re: Filesystems >1TB not possible on 6.0-R (anymore?).

David Kirchner
In reply to this post by Barkley Vowk
FWIW, we have a 6.0-RELEASE machine running now with two 2TB
partitions, using disklabel(bsdlabel) rather than gpt. This is with
the 3ware driver. Could the problem you're having be with the arcmsr
driver in some way? Anyone else on the list using that card able to
confirm it?
_______________________________________________
[hidden email] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[hidden email]"