public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: xfs@oss.sgi.com
Cc: Pascal <pa5ca1@gmx.de>
Subject: Re: Maximum file system size of XFS?
Date: Mon, 11 Mar 2013 23:01:51 +0100	[thread overview]
Message-ID: <201303112301.51715.Martin@lichtvoll.de> (raw)
In-Reply-To: <201303112257.00798.Martin@lichtvoll.de>

Am Montag, 11. März 2013 schrieb Martin Steigerwald:
> Am Montag, 11. März 2013 schrieb Martin Steigerwald:
> > 2) Create a insanely big sparse file
> > 
> > merkaba:~> truncate -s1E /mnt/zeit/evenmorecrazy.img
> > merkaba:~> ls -lh /mnt/zeit/evenmorecrazy.img
> > -rw-r--r-- 1 root root 1,0E Mär 11 22:37 /mnt/zeit/evenmorecrazy.img
> > 
> > (No, this won´t work with Ext4.)
> 
> Okay, you can´t go beyond 8 EiB for a single file which is about what I
> have read somewhere:
[…]
> merkaba:/mnt/zeit> truncate -s7E /mnt/zeit/evenmorecrazy.img
> merkaba:/mnt/zeit> LANG=C truncate -s8E /mnt/zeit/evenmorecrazy.img
> truncate: invalid number '8E': Value too large for defined data type
> merkaba:/mnt/zeit#1> ls -lh
> insgesamt 0
> -rw-r--r-- 1 root root 7,0E Mär 11 22:49 evenmorecrazy.img
> 
> So so tests stops there, until you concatenate two of those files with
> LVM or SoftRAID 0 (if that works). Like this (I just had to try it):
> 
> 
> merkaba:/mnt/zeit> ls -lh
> insgesamt 0
> -rw-r--r-- 1 root root 7,0E Mär 11 22:49 evenmorecrazy.img
> -rw-r--r-- 1 root root 7,0E Mär 11 22:52 evenmorecrazy.img2
> merkaba:/mnt/zeit> losetup /dev/loop0 evenmorecrazy.img
> merkaba:/mnt/zeit> losetup /dev/loop1 evenmorecrazy.img2
> 
> merkaba:/mnt/zeit#5> pvcreate /dev/loop0
>   Physical volume "/dev/loop0" successfully created
> merkaba:/mnt/zeit> pvcreate /dev/loop1
>   Physical volume "/dev/loop1" successfully created
> merkaba:/mnt/zeit> vgcreate justinsane /dev/loop0 /dev/loop1
>   PV /dev/loop0 too large for extent size 4,00 MiB.
>   Format-specific setup of physical volume '/dev/loop0' failed.
>   Unable to add physical volume '/dev/loop0' to volume group
> 'justinsane'.
[…]
> merkaba:/mnt/zeit#5> vgcreate --physicalextentsize 4G  justinsane
> /dev/loop0 /dev/loop1
>   Volume group "justinsane" successfully created
> 
> merkaba:/mnt/zeit> vgs
>   VG         #PV #LV #SN Attr   VSize   VFree
>   justinsane   2   0   0 wz--n-  14,00e 14,00e
>   merkaba      1   4   0 wz--n- 278,99g  4,85g
> merkaba:/mnt/zeit>
> 
> merkaba:/mnt/zeit> vgdisplay justinsane
[…]
> Enough insanity for today :)

Not quite:

> I won´t mkfs.xfs on it, the 20 GiB of the just filesystem wouldn´t be
> enough.

Ok, there seems to be another limit involved:

merkaba:/mnt/zeit> lvcreate -n yourbiggiexfs -L14E justinsane
  Volume group "justinsane" has insufficient free space (3758096382 
extents): 3758096384 required.
merkaba:/mnt/zeit#5> LANG=C lvcreate -n yourbiggiexfs -L14E justinsane
  Volume group "justinsane" has insufficient free space (3758096382 
extents): 3758096384 required.
merkaba:/mnt/zeit#5> LANG=C lvcreate -n yourbiggiexfs -L13E justinsane
  /dev/justinsane/yourbiggiexfs: lseek 0 failed: Invalid argument
  /dev/justinsane/yourbiggiexfs: lseek 0 failed: Invalid argument
  Logical volume "yourbiggiexfs" created
merkaba:/mnt/zeit> LANG=C lvs                                       
  /dev/justinsane/yourbiggiexfs: lseek 14987979559888945152 failed: Invalid 
argument
  /dev/justinsane/yourbiggiexfs: lseek 14987979559889002496 failed: Invalid 
argument
  /dev/justinsane/yourbiggiexfs: lseek 0 failed: Invalid argument
  /dev/justinsane/yourbiggiexfs: lseek 4096 failed: Invalid argument
  /dev/justinsane/yourbiggiexfs: lseek 0 failed: Invalid argument
  LV            VG         Attr      LSize   Pool Origin Data%  Move Log 
Copy%  Convert
  yourbiggiexfs justinsane -wi-a----  13.00e 

So testing with 9 EiB might become some issue :)

Thanks,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2013-03-11 22:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-09 20:51 Maximum file system size of XFS? Pascal
2013-03-09 22:29 ` Ric Wheeler
2013-03-09 22:39   ` Pascal
2013-03-10  1:10     ` Eric Sandeen
2013-03-10  7:54       ` Stan Hoeppner
2013-03-11 11:02         ` Stan Hoeppner
2013-03-11 16:15           ` Hans-Peter Jansen
2013-03-11 16:22             ` Emmanuel Florac
2013-03-11  1:55     ` Dave Chinner
2013-03-11 21:45 ` Martin Steigerwald
2013-03-11 21:57   ` Martin Steigerwald
2013-03-11 22:01     ` Martin Steigerwald [this message]
2013-03-11 22:04       ` Martin Steigerwald
2013-03-20 18:26         ` Pascal
2013-03-11 22:19     ` Dave Chinner
2013-03-11 22:10   ` Martin Steigerwald

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201303112301.51715.Martin@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=pa5ca1@gmx.de \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox