32bit filesystem limitations
bp at barryp.org
Wed Mar 25 12:58:39 PDT 2009
Ivan Voras wrote:
> Andrei Kolu wrote:
>> I created 20GB slice for system and selected everything else for /data
>> but after restart I see again 1,2TB /data. After second sysinstall
>> attempt I created another 2TB slice and now at least I can use whole
>> space. Not so good but it works.
>> Second attempt:
>> Now I reserved 20GB for "boot volume" from 3Ware 9650SE controller and
>> looks like it ...oops...did it again....deem.
>> # df -H
>> Filesystem Size Used Avail Capacity Mounted on
>> /dev/da0s1a 2.1G 146M 1.8G 8% /
>> devfs 1.0k 1.0k 0B 100% /dev
>> /dev/da1s1d 1.2T 4.1k 1.1T 0% /data
>> /dev/da0s1d 3.1G 12k 2.9G 0% /tmp
>> /dev/da0s1f 8.3G 450M 7.2G 6% /usr
>> /dev/da0s1e 4.2G 281k 3.8G 0% /var
> Ok, you're on the right track. Just don't use bsdlabel or fdisk
> partitions for da1 - clear the partition tables and use gpart to create
> a GPT partition tables which has no 32-bit problems.
Is there any reason not to skip labeling/partitioning and use da1
directly? Just newfs it and mount it. I've done this with a couple
large Areca arrays with no ill effect so far.
More information about the freebsd-stable