Re: ext3 max file size?
Tue, 24 May 2011 17:49:11 +0100, Rui Maciel did cat :
Aragorn wrote:
It *does* vary from platform to platform. There's no way around that.
Yes, but is there a way to know what are the file size limits of any
given ext3 file system? To put it differently, if you found yourself
using any random computer which has access to an ext3 partition, is
there a way to check what's the file size limit of that particular ext3
file system?
Rui Maciel
maybe a practical way, eat the pudding and fake a make until error brake?
example (untested):
$ dd if=/dev/zero of=/pathtomountfilesys/dumbig bs=256M count=1 seek=8192
$ dd if=/dev/zero of=/pathtomountfilesys/dumbig bs=128M count=1 seek=8192
$ dd if=/dev/zero of=/pathtomountfilesys/dumbig bs=32M count=1 seek=8192
Maybe chose a smaller block (that may speed up the actual writing but
would slow down the seek time) say:
$ dd if=/dev/zero of=/pathtomountfilesys/dumbig bs=1M count=1 seek=2222000
no time nor place here for a real test so if anyone around there
has a pinch off each he'll may report if that's practical or not ;-)
.
Relevant Pages
- Re: [patch] ext2/3: document conditions when reliable operation is possible
... wouldn't it be an ext3 bug? ... many naive filesystem designers make is that writes succeed or they ... This will obviously cause a write failure, ... No file system will recover that data although you might be able to scrape out some remaining useful bits and bytes. ...
(Linux-Kernel) - Re: want to speed up laptop
... Nearly hit all points on my laptop, ext3 plus ... But I'm not good at tuning the file system. ... There are several factors which combine to hurt overall disk ... Assuming the laptop is reliable, ...
(Debian-User) - Re: Slow ruby regexes
... I don't know about proposed plans for the regexp engine for ruby, ... with one of our sys admins who wanted to use the Riser FS rather than Ext3 as ... the file system on a new server. ... was that file system performance was not a significant bottleneck for the ...
(comp.lang.ruby) - Re: HardBound and SoftBound
... Before ext3, any competent developer understood that until you fsynced a file none of its modifications were guaranteed to be on disk - and most of them understood that this clearly meant that if you renamed a file to overwrite a different file without such an fsync then a crash could leave you with an empty renamed file because metadata updates often were forced to disk faster than content updates. ... And so a lot of incompetent developers just stopped including the fsync, blithely ignoring the fact that this would cause their code to break in any environment *other* than ext3 in this default configuration (i.e., any situation where a different file system was in use or even just one where ext3 was configured to place performance first). ... Along came ext4 and with several other major improvements it fixed the unintentional behavior of ext3, thereby exposing all those relatively recent incompetently-written applications to their just deserts. ...
(comp.arch) - Re: JFS vs EXT3 vs XFS vs ReiserFS
... So, after 3 installs with EXT3, I decided to try something else. ... notice the installer offers JFS, XFS, and ReiserFS, so I picked JFS for ... the most stable and easy to recover file system (and I have stress ... and XFS don't have this problem, and were much faster for hosting large ...
(Ubuntu) |
|
