-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
These days, when I read the source code of mke2fs, I found an option -f
to set the fragment size.
But I can not find any explaining for ext3/4 framgment from google,
excepting someone saying ext2/3 does not support this feature.
Can anyone tell me
On Mon, Jul 30, 2007 at 08:27:47AM -0400, Stephen Smalley wrote:
On Mon, 2007-07-30 at 09:29 +1000, David Chinner wrote:
On Sun, Jul 29, 2007 at 05:02:09PM +0200, Adrian Bunk wrote:
Please correct me if any of the following assumptions is wrong:
- SELinux is currently the only user of
On Aug 01, 2007 21:04 +0530, Aneesh Kumar K.V wrote:
Regarding the naming of tdb file i decided to go with
mke2fs-device_name instead of mke2fs-device_name-time-stamp.
I guess having multiple version of this file in the tdb_dir will confuse
the user.
I thought about this also - it might make
On Aug 01, 2007 14:57 +0200, Bernd Schubert wrote:
saying yes or no to all e2fsck questions can be rather annoying (yes I
know -p and -y), so here's a patch to answer yes or no to a group of
questions.
I've wanted something like this for quite a while already.
What would be more useful,
On Aug 01, 2007 21:04 +0530, Aneesh Kumar K.V wrote:
+static errcode_t write_file_system_identity(io_channel undo_channel,
+ TDB_CONTEXT *tdb)
+{
+ /* Write to tdb file in the file system byte order */
+ tdb_key.dptr = filesystem
Andreas Dilger wrote:
On Aug 01, 2007 14:57 +0200, Bernd Schubert wrote:
saying yes or no to all e2fsck questions can be rather annoying (yes I
know -p and -y), so here's a patch to answer yes or no to a group of
questions.
I've wanted something like this for quite a while already.
Andreas Dilger wrote:
On Aug 01, 2007 21:04 +0530, Aneesh Kumar K.V wrote:
+static errcode_t write_file_system_identity(io_channel undo_channel,
+ TDB_CONTEXT *tdb)
+{
+ /* Write to tdb file in the file system byte order */
+
On Aug 02, 2007 17:55 +0800, Coly Li wrote:
These days, when I read the source code of mke2fs, I found an option -f
to set the fragment size.
But I can not find any explaining for ext3/4 framgment from google,
excepting someone saying ext2/3 does not support this feature.
Can anyone tell
Hi all.
Druing reading the source codes of indirect index, there is a doubt
in my mind. When using indirect index, physical block number must not
exceed 0x, but I cann' t find any clue about how
ext4_alloc_blocks insure that. Codes that check 64bit_feature is only
in ext4_fill_super
From: Jose R. Santos [EMAIL PROTECTED]
Allow FLEX_BG to be use as a feature option at mke2fs time.
Signed-off-by: Jose R. Santos [EMAIL PROTECTED]
--
lib/e2p/feature.c |2 ++
lib/ext2fs/ext2fs.h |6 --
misc/mke2fs.c |3 ++-
3 files changed, 8 insertions(+), 3
From: Jose R. Santos [EMAIL PROTECTED]
Reserve the INCOMPAT feature number for FLEX_BG.
Signed-off-by: Jose R. Santos [EMAIL PROTECTED]
--
lib/ext2fs/ext2_fs.h |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/lib/ext2fs/ext2_fs.h b/lib/ext2fs/ext2_fs.h
index
From: Jose R. Santos [EMAIL PROTECTED]
New bitmap and inode table allocation for FLEX_BG
Change the way we allocate bitmaps and inode tables if the FLEX_BG
feature is used at mke2fs time. The block and inode bitmaps are
allocated as a one contiguous set for each flex block group. Due to
the
12 matches
Mail list logo