lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080718101518.0722e9e4@gara>
Date:	Fri, 18 Jul 2008 10:15:18 -0500
From:	"Jose R. Santos" <jrs@...ibm.com>
To:	Goswin von Brederlow <goswin-v-b@....de>
Cc:	"Theodore Ts'o" <tytso@....edu>, linux-ext4@...r.kernel.org
Subject: Re: [PATCH 15/15][e2fsprogs] 64-bit mke2fs cleanup [NEW Version]

On Fri, 18 Jul 2008 13:35:32 +0200
Goswin von Brederlow <goswin-v-b@....de> wrote:

> "Jose R. Santos" <jrs@...ibm.com> writes:
> 
> > Hi folks,
> >
> > I'm posting a new version of the 64-bit mke2fs patch since it was broken
> > in many ways (many thanks to Goswin for having a look and pointing them
> > out).  This one can actually handle large fs as runs until its time to
> > allocate table (where it barfs due bitmap issues).  To make 64bit fs, I
> > use the following command.
> >
> > mke2fs -T ext4dev -O64bit /dev/my_large_disk
> 
> Just like ext2/3 default to a 4k blocksize if it exceeds 2^32 1k
> blocks shouldn't ext4 default to 64bit if it exceeds 2^32 4k blocks?

Eventually, when the feature is stable enough, we can change the
default in mke2fs.conf to include this feature for the ext4 fs_type.
The problem of setting it only if the fs exceeds 2^32 blocks is that
you will not be able to resize an fs from 32 to 64bit due to the block
group descriptor size change.  Once the feature is stable, it should
set as default regardless of the storage size.
 
> > Comments welcome 
> >
> > -JRS
> 
> MfG
>         Goswin


-JRS
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ