From: Gordon Ross (G.Ross_at_ccw.gov.uk)
Date: Tue Mar 13 2007 - 11:45:46 CET
Message-Id: <45F680D9.AC0B.0006.3@ccw.gov.uk> Date: Tue, 13 Mar 2007 10:45:46 +0000 From: "Gordon Ross" <G.Ross@ccw.gov.uk> Subject: Re: [suse-sles-e] Filesystem limitations on SLES 10
>>> On 13 March 2007 at 10:25, in message
<200703131125.42009.rafagriman@gmail.com>, Rafa Grimán <rafagriman@gmail.com>
wrote:
> Hi :)
>
> El Tuesday 13 March 2007, Gordon Ross escribió:
>> I've got a 64-bit, SLES 10 server.
>>
>> Attached to it, is an external RAID array, with a 4.7TB volume
>> presented to the O/S. We've been having "fun" trying to create
>> partitions/filesystems on this thing.
>
> [...]
>
>> According to http://www.novell.com/linux/kernel_limits.html we should
>> have had no problems at all.
>>
>> Can anyone explain what's going on ? I'm guessing that the kernel can
>> support very large filesystems, it's just the userspace stuff that
>> can't... However, a 4.7 TB filesystem surely isn't that uncommon
>> nowadays ?
>
>
> What storage system do you have attached? Does it support LUNs > 2 TB?
>
> This could be the issue. If it doesn't support >2TB LUNs then you'll have to
> create 3 LUNs (1.5 + 1.5 + 1.7 or 2 + 2 + 0.7 or whatever combination) and
> then use some volume manager (LVM, for example) to bind them together and
> get
> your 4+ TB filesystem.
It's a simple SATA RAID array presented as SCSI (nothing clever) It does support 4TB volumes. As you can see:
ns@hq-hls1:~> df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/system-root
9.9G 3.9G 5.5G 42% /
udev 4.9G 132K 4.9G 1% /dev
/dev/cciss/c0d0p1 251M 8.5M 230M 4% /boot
/dev/mapper/system-opt
40G 5.2G 33G 14% /usr
/dev/mapper/system-var
5.0G 249M 4.5G 6% /var
/dev/sdc1 4.8T 1.5T 3.4T 31% /discs/sata0
GTG
---------------------------------------------------------------------
To unsubscribe, e-mail: suse-sles-e-unsubscribe@suse.com
For additional commands, e-mail: suse-sles-e-help@suse.com
This archive was generated by hypermail 2.1.7 : Tue Mar 13 2007 - 13:50:05 CET