ro_bit needs an aligned address on some arch
Mingming Cao (1):
ext4: Fix BUG when writing to an unitialized extent
Theodore Ts'o (1):
ext4: Don't use ext4_dec_count() if not needed
Valerie Clement (2):
ext4: Fix kernel BUG at fs/ext4/mballoc.c:910!
ext4: modify block
then
apply this patch against that.
- Ted
commit 09138f9e096af809f1ff02df9194c9e0dad186db
Author: Theodore Ts'o <[EMAIL PROTECTED]>
Date: Tue Feb 19 08:32:58 2008 -0500
New mke2fs types parsing --- IN PROGRESS
diff --git a/misc/mke2fs.c b/misc/mke2fs.c
ind
I've started testing my in-development extents against the test cases
found in clusterfs's e2fsprogs patches, and I noticed that with
f_extents (the first one I tried), some of the inodes had non-zero
ee_start_hi fields. (That is to say, they had block numbers in the
extents fields that were much
fix for large block support
ext4: remove read-inode from defrag code,replace with ext4_iget()
Theodore Ts'o (2):
ext4: Stable/Unstable boundary
ext4: New inode allocation for FLEX_BG meta-data groups.
fs/buffer.c |3 +-
fs/ext4/Mak
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git for_linus
These are mostly bug fixes that we've found since the last pull request.
The one non-bugfix change is that I've added a sanity check to assure
that production ext3 filesystems don't get mou
opriate
forward compatibility when sometime (hopefully 2.6.26 or 2.6.27?) we
rename ext4dev to ext4.
Any comments before I push this change out to the maint branch?
- Ted
commit feac6e49211a44ef6f560b3b362fb132a474a471
Author: Theodore Ts'o <[EMAIL
ing Cao (2):
jbd: blocks reservation fix for large block support
jbd2: blocks reservation fix for large block support
Theodore Ts'o (5):
* ext4: Replace use of iget() with iget_locked()
* jbd2: Add error check to journal_wait_on_commit_record to avoid oops
patch test-fil
FYI, since iget() is going to be disappearing in 2.6.25, and akpm has
disabled ext4 in the -mm tree as a result, I'm folding the following
patch into the defrag-free-space-fragmentation.patch in the ext4 tree.
We also have an issue where the read-only bind patches from Dave Hansen
are making chan
In the mm tree is a patch queued up to nuke iget(). So replace use of
iget() with iget_locked(). I will be pushing this to Linus shortly.
- Ted
commit 46ea772acbda42780ae014e608f51e71083be46b
Author: Theodore Ts'o <[EMAIL PROTECTED]>
ode
Mingming Cao (2):
jbd: blocks reservation fix for large block support
jbd2: blocks reservation fix for large block support
Theodore Ts'o (2):
patch test-filesys-flag.patch
ext4: New inode allocation for FLEX_BG meta-data groups.
fs/buffer.c
I've just released 2.6.24-ext4-1. It's basically just a clean up of the
stable patch series, in response to LKML review comments, in preparation
for Linus to pull them into mainline.
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git 2.6.24-ext4-1
http://git.kernel.org/?p=linux/kerne
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git for_linus
This is the major set of updates meant for 2.6.24 from the ext4 team;
these patches have been baking in -mm for a while. The two major
features included here is the multi-block allocator
I was trying to build ext4 as a module, and ran into problems because
the online defrag patch is calling do_fsync() which is *not* an exported
symbol, and so can not be called from a module.
Looking at what the routine is doing, there's no reason to call
do_fsync(), and in fact depending on the j
From: Jan Kara <[EMAIL PROTECTED]>
Before we start committing a transaction, we call
__journal_clean_checkpoint_list() to cleanup transaction's written-back
buffers.
If this call happens to remove all of them (and there were already some
buffers), __journal_remove_checkpoint() will decide to free
From: Aneesh Kumar K.V <[EMAIL PROTECTED]>
This function is used by the ext4 multi block allocator patches.
Also add generic_find_next_le_bit
Signed-off-by: Aneesh Kumar K.V <[EMAIL PROTECTED]>
Cc:
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---
include/asm-arm/bitops.h
patch description should be free-standing,
and describe the specific patch in question.
- Ted
commit a5cab2d59b7fb032f507933d5d2b1590edbf9036
Author: Theodore Ts'o <[EMAIL PROTECTED]>
Date: Mon Jan 21 10:31:58 2008 -0500
Fix up patch com
heuristics
Samuel Thibault (1):
Fix Debian rules files to support building non-Linux archs
Theodore Ts'o (20):
Fix errors in test_ss.c so it can be an example application and
test case
libext2fs: Fix a corner case bug in ext2fs_unlink
libss: Fix parallel build failure
Update Span
* The 'maint' branch has these fixes since the last announcement.
Theodore Ts'o (1):
Fix typo in the summary section of the blkid man page
* The 'master' branch has these since the last announcement
in addition to the above.
Valerie Clement (3):
libext2fs: use
Here are the topics that have been cooking. Commits prefixed
with '-' are only in 'pu' while commits prefixed with '+' are
in 'next'. The topics list the commits in reverse chronological
order.
* next (Sun Oct 21 21:03:14 2007 -0500) 6 commits
(plus those commits pulled in from the topic
Could people please use more descriptive names for patch names? Names
like:
ext4-cleanup-2.patch
ext4-cleanup-3.patch
ext4-cleanup-4.patch
aren't very useful when browsing through the series file.
Thanks,
- Ted
-
To unsubscribe from this list: send the
I've just released 2.6.24-rc1-ext4-1. It removes patches accepted by
Linus and adds a number of cleanup patches. It also adds support for
storing i_blocks in units of filesystem blocks instead of 512 byte
sectors to eliminate one stupid (and easy to fix) large file scalability
limit.
git://git.
The strtoul() function has a lot of messy error checking that needs to
be done; by factoring it out into one place we can make sure it's done
right in all of the places where it is called.
Signed-off-by: "Theodore Ts'o" <[EMAIL PROTECTED]>
--
This will make it easier for us to support 64-bit block numbers when
the time comes. Not that running badblocks on a > 4TB machine is
anything I want to contemplate!
Signed-off-by: "Theodore Ts'o" <[EMAIL PROTECTED]>
---
Signed-off-by: "Theodore Ts'o" <[EMAIL PROTECTED]>
---
misc/badblocks.c | 22 +++---
1 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/misc/badblocks.c b/misc/badblocks.c
index 29c5a5c..155fb77 100644
--- a/misc/badblocks.c
+++ b/misc/badbl
, although the exit status will still be
non-zero.
Addresses-Red-Hat-Bugzilla: #180596
Signed-off-by: "Theodore Ts'o" <[EMAIL PROTECTED]>
Signed-off-by: Eric Sandeen <[EMAIL PROTECTED]>
---
misc/chattr.1.in |7 ++--
misc/chattr.c| 83 +
To allow error messages to be reflected up, if the callback function
returns a non-zero value, bump a counter and return the number of
times the callback function signals an error by returning a non-zero
status code.
Signed-off-by: "Theodore Ts'o" <[EMAIL PROTECTED]>
---
We can't set the flags on symbolic links, so check for them using
lstat().
Signed-off-by: "Theodore Ts'o" <[EMAIL PROTECTED]>
---
lib/e2p/fgetflags.c |2 +-
lib/e2p/fsetflags.c |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/lib/e2p/fgetfla
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git for_linus
It has a number random cleanups and bug fixes, and two new features.
The first is uninitialized block groups, which allows fast mke2fs
operations plus as well as speeding up e2fsck by allow
Here are the topics that are cooking in e2fsprogs. Commits prefixed
with '-' are only in 'pu' while commits prefixed with '+' are in
'next'. Commits prefixed with '.' are not in either branch for now.
* tt/64bit-bitmaps (Sun Oct 14 22:51:51 2007 -0400) 1 commit
- Initial design for 64-bit bitm
I've just released the 2.6.23-rc9-ext4-1. It collapses some patches in
preparation for pushing them to Linus, and adds some of cleanup patches
that had been incorporated into Andrew's broken-out-2007-10-01-04-09
series. It also has some new development patches in the unstable (not
yet ready to p
From: Jan Kara <[EMAIL PROTECTED]>
With 64KB blocksize, a directory entry can have size 64KB which does not fit
into 16 bits we have for entry lenght. So we store 0x instead and convert
value when read from / written to disk. The patch also converts some places
to use ext3_next_entry() when we
From: Coly Li <[EMAIL PROTECTED]>
implement in future. Therefore fragment related source code in ext4 should
be obsoleted -- no one will use it.
This patch obsolete fragment from ext4. Another patch posted on linux-ext4
removing fragment supporting from e2fsprogs.
Signed-off-by: Coly Li <[EMAI
From: Andreas Dilger <[EMAIL PROTECTED]>
In pass1 of e2fsck, every inode table in the fileystem is scanned and checked,
regardless of whether it is in use. This is this the most time consuming part
of the filesystem check. The unintialized block group feature can greatly
reduce e2fsck time by el
From: Jose R. Santos <[EMAIL PROTECTED]>
data is located within the storage media. This allows for the allocation
of bitmaps or inode tables outside the block group boundaries in cases
where bad blocks forces us to look for new blocks which the owning block
group can not satisfy. This will also
From: Takashi Sato <[EMAIL PROTECTED]>
This patch set supports large block size(>4k, <=64k) in ext3
just enlarging the block size limit. But it is NOT possible to have 64kB
blocksize on ext3 without some changes to the directory handling
code. The reason is that an empty 64kB directory block woul
ric Sandeen <[EMAIL PROTECTED]>
Signed-off-by: Mingming Cao <[EMAIL PROTECTED]>
Signed-off-by: "Theodore Ts'o" <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---
fs/ext4/dir.c |7 ---
fs/ext4/namei.c | 20 --
From: Takashi Sato <[EMAIL PROTECTED]>
This patch set supports large block size(>4k, <=64k) in ext2,
just enlarging the block size limit. But it is NOT possible to have 64kB
blocksize on ext2 without some changes to the directory handling
code. The reason is that an empty 64kB directory block wou
From: Jan Kara <[EMAIL PROTECTED]>
With 64KB blocksize, a directory entry can have size 64KB which does not fit
into 16 bits we have for entry lenght. So we store 0x instead and convert
value when read from / written to disk.
Signed-off-by: Jan Kara <[EMAIL PROTECTED]>
Signed-off-by: Mingming
From: Jan Kara <[EMAIL PROTECTED]>
With 64KB blocksize, a directory entry can have size 64KB which does not fit
into 16 bits we have for entry lenght. So we store 0x instead and convert
value when read from / written to disk. The patch also converts some places
to use ext4_next_entry() when we
From: Takashi Sato <[EMAIL PROTECTED]>
This patch set supports large block size(>4k, <=64k) in ext4,
just enlarging the block size limit. But it is NOT possible to have 64kB
blocksize on ext4 without some changes to the directory handling
code. The reason is that an empty 64kB directory block wou
From: Jose R. Santos <[EMAIL PROTECTED]>
Mostly stolen from akpm's JBD cleanup patch.
- use `#ifdef foo' instead of `#if defined(foo)'
- Make journal_enable_debug __read_mostly just for the heck of it
- Make jbd_debugfs_dir and jbd_debug static
- debugfs_remove(NULL) is legal: remove unneeded
From: Aneesh Kumar K.V <[EMAIL PROTECTED]>
Signed-off-by: Aneesh Kumar K.V <[EMAIL PROTECTED]>
---
fs/ext4/fsync.c |2 +-
fs/ext4/inode.c |2 +-
fs/ext4/xattr.c |4 ++--
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/fs/ext4/fsync.c b/fs/ext4/fsync.c
index 2a167d7..8d5
From: Aneesh Kumar K.V <[EMAIL PROTECTED]>
Convert bg_block_bitmap to bg_block_bitmap_lo
This helps in catching some BUGS due to direct
partial access of these split fields.
Signed-off-by: Aneesh Kumar K.V <[EMAIL PROTECTED]>
---
fs/ext4/super.c |6 +++---
include/linux/ext4_fs.h |
From: Aneesh Kumar K.V <[EMAIL PROTECTED]>
Convert ext4_extent.ee_start to ext4_extent.ee_start_lo
This helps in finding BUGs due to direct partial access of
these split 48 bit values
Also fix direct partial access in ext4 code
Signed-off-by: Aneesh Kumar K.V <[EMAIL PROTECTED]>
---
fs/ext4/ext
From: Aneesh Kumar K.V <[EMAIL PROTECTED]>
Convert s_blocks_count to s_blocks_count_lo
This helps in finding BUGs due to direct partial access of
these split 64 bit values
Also fix direct partial access in ext4 code
Signed-off-by: Aneesh Kumar K.V <[EMAIL PROTECTED]>
---
fs/ext4/super.c
From: Aneesh Kumar K.V <[EMAIL PROTECTED]>
Convert s_r_blocks_count and s_free_blocks_count to
s_r_blocks_count_lo and s_free_blocks_count_lo
This helps in finding BUGs due to direct partial access of
these split 64 bit values
Also fix direct partial access in ext4 code
Signed-off-by: Aneesh Ku
From: Aneesh Kumar K.V <[EMAIL PROTECTED]>
Signed-off-by: Aneesh Kumar K.V <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---
fs/ext4/inode.c |6 --
include/linux/ext4_fs.h | 14 +++---
2 files changed, 11 insertions(+), 9 deletions(-)
diff --git a
From: Aneesh Kumar K.V <[EMAIL PROTECTED]>
Convert ext4_extent_idx.ei_leaf ext4_extent_idx.ei_leaf_lo
This helps in finding BUGs due to direct partial access of
these split 48 bit values.
Signed-off-by: Aneesh Kumar K.V <[EMAIL PROTECTED]>
---
fs/ext4/extents.c |4 ++--
includ
The following ext4 patches are planned for submission to Linus once
the merge window for 2.6.24-rc1 is opened.
- Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to [EMAIL PROTECTED]
More majordom
From: Mingming Cao <[EMAIL PROTECTED]>
JBD: Replace slab allocations with page cache allocations
JBD allocate memory for committed_data and frozen_data from slab. However
JBD should not pass slab pages down to the block layer. Use page allocator
pages instead. This will also prepare JBD for the
From: Jan Kara <[EMAIL PROTECTED]>
We should really call journal_abort() and not __journal_abort_hard() in
case of errors. The latter call does not record the error in the journal
superblock and thus filesystem won't be marked as with errors later (and
user could happily mount it without any warn
From: Mingming Cao <[EMAIL PROTECTED]>
Convert kmalloc to kzalloc() and get rid of the memset().
Signed-off-by: Mingming Cao <[EMAIL PROTECTED]>
---
fs/ext4/xattr.c |3 +--
fs/jbd2/journal.c |3 +--
fs/jbd2/transaction.c |3 +--
3 files changed, 3 insertions(+), 6 deletions
From: Aneesh Kumar K.V <[EMAIL PROTECTED]>
Convert bg_inode_bitmap and bg_inode_table to bg_inode_bitmap_lo
and bg_inode_table_lo. This helps in finding BUGs due to
direct partial access of these split 64 bit values
Also fix one direct partial access
Signed-off-by: Aneesh Kumar K.V <[EMAIL PROT
From: Aneesh Kumar K.V <[EMAIL PROTECTED]>
Signed-off-by: Mingming Cao <[EMAIL PROTECTED]>
Signed-off-by: "Theodore Ts'o" <[EMAIL PROTECTED]>
---
fs/jbd/journal.c |2 +-
fs/jbd2/journal.c |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff
Here's an initial code review of the mballoc-core.patch. As far as I
can tell, the patch sent by Aneesh doesn't address any of these.
Aneesh, assuming that you'll be fixing these, could you please combine
your last set of fixes with fixes to address these, and send out an
updated mballoc-core.pat
I've just released the 2.6.23-rc7-ext4-1; it's largely identical to
2.6.23-rc6-ext4-1 except that I've synchronized patches and patch names
with patches that Andrew had pulled into 2.6.23-rc7-mm1.
It's available in the standard place:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git
doesn't need __GFP_NOFAIL
+
+Signed-off-by: Mingming Cao <[EMAIL PROTECTED]>
+Signed-off-by: "Theodore Ts'o" <[EMAIL PROTECTED]>
+
---
fs/jbd/journal.c |2 +-
fs/jbd2/journal.c |2 +-
diff --git a/jbd_kmalloc_kzalloc.patch b/jbd_kmalloc_kzalloc.patch
ind
FYI, I updated the mballoc-core patch in the ext4-patch-queue to not try
to pull in both ext4_jbd2.h and jbd.h; this was causing duplicate
definition, so I removed the #include of jbd.h
- Ted
Remove #include of linux/jbd.h from mballoc-core so it will
g Cao <[EMAIL PROTECTED]>
change JBD_XXX macros to JBD2_XXX in JBD2/Ext4
Signed-off-by: Mingming Cao <[EMAIL PROTECTED]>
Signed-off-by: "Theodore Ts'o" <[EMAIL PROTECTED]>
---
diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c
index 78beb09..2be404f 100644
--- a/fs/
I've pushed out a new ext4 patchset, based off of 2.6.23-rc7. I had to
fix a number of patch application errors and compile-time errors in the
ext4 patch queue; I'll send mail separately about each of those fix ups.
It's available in the standard place:
git://git.kernel.org/pub/scm/linux/kernel
Factor out code to clear a bogus inode and update e2fsck's internal
data structures accordingly into a common routine,
e2fsck_clear_inode(). This saves about 200 bytes in the compiled x86
e2fsck executable, and makes the code more maintainable in the
long-term.
Signed-off-by: "The
d
+ * thus we make it as a special case of initialized extent with 0x8000 length.
+ * This way we get better extent-to-group alignment for initialized extents.
+ * Hence, the maximum number of blocks we can have in an *initialized*
+ * extent is 2^15 (32768) and in an *uninitialized* extent is 2^15-1
to be a pointer to the ss_request_table.
In addition, the symbol debug_prog_name can be used to override the
name of the program printed in the version banner and in the ss
prompt.
Signed-off-by: "Theodore Ts'o" <[EMAIL PROTECTED]>
---
debugfs/debugfs.c | 21
extents, etc. So to avoid needing to
expose all of that complexity in swapfs.c, the in-memory contents of
i_blocks will not be byte-swapped and will be identical to the on-disk
format.
Signed-off-by: "Theodore Ts'o" <[EMAIL PROTECTED]>
---
lib/ext2fs/swapfs.c |4 +++
For people who are curious about how the extents patch for e2fsprogs
is going, here's what I currently have as a work in progress. With
this patch, e2fsck will currently correctly handle a valid filesystem
that contains extents, but it's missing a lot of sanity checks. In
particular, the pass1b
I've been busy working on extents support in e2fsck, and so as part of
that I was looking at the clusterfs extent patches (mostly for
inspiration to see how they work). One of the things which I noticed is
the patches seem to check the inode direct blocks, and if they look like
the extent header,
Hi there,
There was recent discussion of taking out support for "dead" OS's and
features in e2fsprogs, such as fragmentation, support for the Masix
OS and Hurd. So in the interests of doing some research to see
whether or not Hurd was really completely dead, or just "mostly dead"
(to in the P
Signed-off-by: "Theodore Ts'o" <[EMAIL PROTECTED]>
---
lib/ext2fs/rw_bitmaps.c | 46 --
1 files changed, 0 insertions(+), 46 deletions(-)
diff --git a/lib/ext2fs/rw_bitmaps.c b/lib/ext2fs/rw_bitmaps.c
index 603b590..1897ec3 10
This removes the last vestiges of support for the legacy PowerPC
big-endian filesystem format.
Signed-off-by: "Theodore Ts'o" <[EMAIL PROTECTED]>
---
configure | 33 ++---
configure.in | 20
debian/r
The need for fixing byte-swapped filesystems is long-gone, and this is
getting in the way of cleaning up e2fsprogs's bitmaps code. So let's
get rid of it; modern kernels haven't been able to deal with a
byte-swapped filesystem in in about 9 years.
Signed-off-by: "Theodore Ts&
We don't need byte swapping to be a run-time option; it can just be a
compile-time option instead.
Signed-off-by: "Theodore Ts'o" <[EMAIL PROTECTED]>
---
lib/ext2fs/bmap.c | 28 ++---
lib/ext2fs/closefs.c | 77 -
Signed-off-by: "Theodore Ts'o" <[EMAIL PROTECTED]>
---
debugfs/logdump.c |2 +-
e2fsck/journal.c |2 +-
e2fsck/util.c |2 +-
misc/dumpe2fs.c |7 ---
misc/e2image.c|8 +++-
5 files changed, 6 insertions(+), 15 deletions(-)
diff --git
Signed-off-by: "Theodore Ts'o" <[EMAIL PROTECTED]>
---
tests/f_swapfs/debugfs.cmd |5 --
tests/f_swapfs/expect | 133
tests/f_swapfs/image | Bin 1048576 -> 0 bytes
tests/f_swapfs/image.gz| Bin 3777 -> 0
>It turns out the need for this was only in the very first ports of
>Linux to the Powerpc, and there haven't been kernels that would mount
>big-endian superblocks since, oh, 1998 or so (in the 2.0 days).
>
>So probably the better fix is one where we don't allow big-endian
>filesystems any more. On
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git for_linus
Many thanks!!
- Ted
Eric Sandeen (2):
Fix fencepost error in ext[234]_check_descriptors
Remove unused bh in calls to ext[234]_g
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git for_linus
It contains the following feature enhancements, including support for
the new fallocate() system call. These have been in -mm for a while,
consensus reached for the fallocate() interface b
E2fsprogs 1.40.2 has been released. It can be downloaded from one of
the following sites:
http://prdownloads.sourceforge.net/e2fsprogs/e2fsprogs-1.40.2.tar.gz
ftp://ftp.kernel.org/pub/linux/kernel/people/tytso/e2fsprogs/e2fsprogs-1.40.2.tar.gz
Release notes follow...
E2fsprogs 1.40.2 (July 12
Per our discussion on the call, I've moved the fallocate patches back up
to the front of the queue, and rebased the syscall numbers to 2.6.22.
So we're just waiting for Amit to make the minor on-disk format change
Andreas suggested before we push to Linus.
People may have noticed that e2fsprogs 1.40 and roughly a week later
e2fsprogs 1.40.1 have been released, while there hasn't been any
activity at http://thunk.org/hg/e2fsprogs. That's because right after
e2fsprogs 1.40, I have moved the e2fsprogs development activity over to
git. The public repos
The hg repository located at:
http://thunk.org/hg/e2fsprogs
... contains what I hope to be the e2fsprogs 1.40 release. If folks
could test it and let me know if they find any embarassing bugs, I would
greatly appreciate it. It can also be found at:
ftp://ftp.kernel.org/pub/linux/kerne
I've released the 2.6.22-rc4-ext4-1 tree, which can be downloaded from
the usual place:
http://ftp.kernel.org/pub/linux/kernel/people/tytso/ext4-patches
This is just a rebase versus 2.6.22-rc4, and reflects the bugfix patches
that have been accepted into mainline.
t4: Extent overlap bugfix
Dave Kleikamp (1):
EXT4: Fix whitespace
Mingming Cao (1):
Remove unnecessary exported symbols.
Theodore Ts'o (1):
Define/reserve new ext4 superblock fields
-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the bo
Per last week's conference call, I've included an update of the
e2fsprogs patchset to support extents. It still needs more work before
it can be folded into mainline, but I'm including them so that people
can see which way I'm headed, and because debugfs has been enhaced to
show extents, which c
I've respun the ext4 development patchset, with Amit's updated fallocate
patches. I've added Dave's patch to add ia64 support to the fallocate
system call, but *not* the XFS fallocate support patches. (Probably
better for them to live in an xfs tree, where they can more easily
tested and updated
For a while now, I've been receiving complaints from users who have been
using BackupPC, or some other equivalent backup progam which functions
by using hard links to create incremental backups. (There may be some
people who are using rsync to do the same thing; if you know of other
such backup p
There is a newly updated ext4 patchset available at:
http://www2.kernel.org/pub/linux/kernel/people/tytso/ext4-patches
and
http://www2.kernel.org/git/?p=linux/kernel/git/tytso/ext4.git
Compared to 2.6.20-ext4-1, I've removed the the i_version patch, since
they had numerous issu
of acceptance: December 15, 2006
Workshop Organizers
Program Chair
Ric Wheeler, EMC
Program Committee
Jens Axboe, Oracle
James Bottomley, SteelEye
Valerie Henson, Intel
Andrew Morton, Google
Trond Myklebust, Network Appliance
Brian Pawlowski, Network Appliance
Theodore Ts'o, IBM
Overview
fields in large inodes
(for nsec+epoch timestamps, potential other uses). Needs RO_COMPAT
flag handling, needs e2fsck support, patch complete, little testing.
Signed-off-by: "Theodore Ts'o" <[EMAIL PROTECTED]>
Index: e2fsprogs
cts old filesystems from unlinking such
directories incorrectly and losing all files therein.
Signed-off-by: "Theodore Ts'o" <[EMAIL PROTECTED]>
Index: e2fsprogs/lib/ext2fs/ext2_fs.h
===
--- e2fsprogs.orig/lib/
)). This allows the kernel to more safely
manage UNINIT groups.
Signed-off-by: "Theodore Ts'o" <[EMAIL PROTECTED]>
Index: e2fsprogs/lib/ext2fs/ext2_fs.h
===
--- e2fsprogs.orig/lib/ext2fs/ext2_fs.h 2006-10-18 02:
part of 64BIT).
Signed-off-by: "Theodore Ts'o" <[EMAIL PROTECTED]>
Index: e2fsprogs/lib/ext2fs/ext2_fs.h
===
--- e2fsprogs.orig/lib/ext2fs/ext2_fs.h 2006-10-18 02:20:25.0 -0400
+++ e2fsprogs/lib/ext2fs/e
nt_hi),
large group descriptors (s_desc_size), extents with high 16 bits
(ee_start_hi, ei_leaf_hi), inode ACL (i_file_acl_hi). May also grow
to encompass the previously proposed BIG_BG.
Signed-off-by: "Theodore Ts'o" <[EMAIL PROTECTED]>
Index: e2fs
Some of the new on-disk format changes are chewing up some of the inode
fields that had been previously reserved for fragments, which has
started me thinking about whether this would box us in if we ever wanted
to implement extents --- for example, if we start seeing 64k blocksize
filesystems and
, and this allows for a cleaner data structure on disk.
Signed-off-by: "Theodore Ts'o" <[EMAIL PROTECTED]>
Index: e2fsprogs/lib/ext2fs/ext2_fs.h
===
--- e2fsprogs.orig/lib/ext2fs/ext2_fs.h 2006-10-11 01:29:36.000
d patch, but
hopefully it isn't required at all.
Regards,
- Ted
--
Add checks to see if the partition is in use by Lustre
Signed-off-by: Andreas Dilger <[EMAIL PROTECTED]>
Signed-off-by: "Theodore Ts'o&q
So I've been noodling over Andreas' patches to support 32-bit extents,
as well as glancing at the 48-bit and 64-bit patches, and I've come to
an initial plan for how to fold this into e2fsprogs in the most
ABI-preserving, backwards compatible way possible. This does mean that
the patches will have
96 matches
Mail list logo
