On Wed, 2007-07-11 at 00:38 -0500, Jose R. Santos wrote:
On Tue, 10 Jul 2007 16:30:25 -0700
Andrew Morton [EMAIL PROTECTED] wrote:
On Sun, 01 Jul 2007 03:36:48 -0400
Mingming Cao [EMAIL PROTECTED] wrote:
On Jun 07, 2007 23:45 -0500, Jose R. Santos wrote:
The jbd2-debug file
On Tue, 2007-07-10 at 23:35 -0400, Dave Jones wrote:
On Tue, Jul 10, 2007 at 05:35:13PM -0400, Mingming Cao wrote:
Sorry about this. I was using version 0.04. The latest one I can find
for now is 0.05(searching lkml), but it didn't catch this codling style
bug either. I appreciate if
On Tue, 2007-07-10 at 22:17 -0700, Andrew Morton wrote:
On Tue, 10 Jul 2007 22:09:08 -0400 Mingming Cao [EMAIL PROTECTED] wrote:
David Chinneer pointed that we need to journal the version number
updates together with the operations that causes the change of the inode
version number, in
On Sun, 01 Jul 2007 03:38:51 -0400 Mingming Cao [EMAIL PROTECTED] wrote:
Subject: [EXT4 set 9][PATCH 4/5]Morecleanups:ext4_extent_compilation_fixes
Date: Sun, 01 Jul 2007 03:38:51 -0400
Sender: [EMAIL PROTECTED]
Organization: IBM Linux Technology Center
X-Mailer: Evolution 2.8.0
On Sun, 01 Jul 2007 03:38:59 -0400 Mingming Cao [EMAIL PROTECTED] wrote:
From: Dmitry Monakhov [EMAIL PROTECTED]
Subject: ext4: extent macros cleanup
- Replace math equation to it's macro equivalent
s/it's/its/;)
- make ext4_ext_grow_indepth() indexes/leaf correct
hm, what was wrong with
On Tue, 10 Jul 2007 23:18:50 -0400 Mingming Cao [EMAIL PROTECTED] wrote:
On Tue, 2007-07-10 at 22:17 -0700, Andrew Morton wrote:
On Tue, 10 Jul 2007 22:09:08 -0400 Mingming Cao [EMAIL PROTECTED] wrote:
David Chinneer pointed that we need to journal the version number
updates together
On Wed, Jul 11, 2007 at 12:10:34PM +1000, Stephen Rothwell wrote:
On Wed, 11 Jul 2007 01:50:00 +0530 Amit K. Arora [EMAIL PROTECTED] wrote:
--- linux-2.6.22.orig/arch/x86_64/ia32/sys_ia32.c
+++ linux-2.6.22/arch/x86_64/ia32/sys_ia32.c
@@ -879,3 +879,11 @@ asmlinkage long
On Tue, Jul 03, 2007 at 05:16:50PM +0530, Amit K. Arora wrote:
Well, if you see the modes proposed using above flags :
#define FA_ALLOCATE 0
#define FA_DEALLOCATE FA_FL_DEALLOC
#define FA_RESV_SPACE FA_FL_KEEP_SIZE
#define FA_UNRESV_SPACE (FA_FL_DEALLOC | FA_FL_KEEP_SIZE |
On Mon, Jul 02, 2007 at 08:55:43AM +1000, David Chinner wrote:
Given the current behaviour for posix_fallocate() in glibc, I think
that retaining the same error semantic and punting the cleanup to
userspace (where the app will fail with ENOSPC anyway) is the only
sane thing we can do here.
On Wed, Jul 04, 2007 at 03:37:01PM +1000, Timothy Shimmin wrote:
We use this capability in XFS at the moment.
I think this is mainly for DMF (HSM) but is done via the xfs handle
interface
(xfs_open_by_handle) AFAICT.
You're not :) You're using an O_INVIBLE equivalent (as described below),
Hello everybody,
sorry for this question if it has been asked before; I couldn't find
information about this.
Please keep me CC'ed - I'm not subscribed. Thank you.
Ext2/3 have ext2resize/resize2fs, ext2prepare and ext3online for resizing.
But they don't work for ext4.
Here's a sample output
Hi Ted,
Following patch implement the Undo I/O manager and undoe2fs.
The patches are on top of latest git(23edf9b4674ced1cdf8625bd609d95dbd62923b3)
-aneesh
-
To unsubscribe from this list: send the line unsubscribe linux-ext4 in
the body of a message to [EMAIL PROTECTED]
More majordomo
From: Aneesh Kumar K.V [EMAIL PROTECTED]
undoe2fs can be used to replay the transaction saved
in the transaction file using undo I/O Manager
Signed-off-by: Aneesh Kumar K.V [EMAIL PROTECTED]
---
misc/Makefile.in | 10 --
misc/undoe2fs.c | 48
On Jul 10, 2007 16:30 -0700, Andrew Morton wrote:
+#define EXT4_FITS_IN_INODE(ext4_inode, einode, field) \
+ ((offsetof(typeof(*ext4_inode), field) +\
+ sizeof((ext4_inode)-field)) \
+ = (EXT4_GOOD_OLD_INODE_SIZE + \
+
On Jul 10, 2007 23:34 -0400, Trond Myklebust wrote:
On Wed, 2007-07-11 at 13:21 +1000, Neil Brown wrote:
So my vote is to increment i_version in common code every time any
change is made to the file, and alloc_inode should initialise it to
current time, which might be changed by the
On Jul 10, 2007 16:31 -0700, Andrew Morton wrote:
This patch adds 64-bit inode version support to ext4. The lower 32 bits
are stored in the osd1.linux1.l_i_version field while the high 32 bits
are stored in the i_version_hi field newly created in the ext4_inode.
So reading the code here
On Jul 11, 2007 09:47 +0100, Christoph Hellwig wrote:
On Sun, Jul 01, 2007 at 03:37:45AM -0400, Mingming Cao wrote:
This patch is on top of i_version_update_vfs.
The i_version field of the inode is set on inode creation and incremented
when the inode is being modified.
Which is not what
On Wed, 2007-07-11 at 09:47 +0100, Christoph Hellwig wrote:
On Sun, Jul 01, 2007 at 03:37:45AM -0400, Mingming Cao wrote:
This patch is on top of i_version_update_vfs.
The i_version field of the inode is set on inode creation and incremented
when
the inode is being modified.
Which is
On Jul 10, 2007 16:31 -0700, Andrew Morton wrote:
On Sun, 01 Jul 2007 03:37:53 -0400
Mingming Cao [EMAIL PROTECTED] wrote:
Add a noversion mount option to disable inode version updates.
Why is this option being offered to our users? To reduce disk traffic,
like noatime?
If so, what
On Wed, Jul 11, 2007 at 05:52:24AM -0600, Andreas Dilger wrote:
On Jul 11, 2007 09:47 +0100, Christoph Hellwig wrote:
On Sun, Jul 01, 2007 at 03:37:45AM -0400, Mingming Cao wrote:
This patch is on top of i_version_update_vfs.
The i_version field of the inode is set on inode creation and
On Jul 10, 2007 16:32 -0700, Andrew Morton wrote:
err = ext4_reserve_inode_write(handle, inode, iloc);
+ if (EXT4_I(inode)-i_extra_isize
+ EXT4_SB(inode-i_sb)-s_want_extra_isize
+ !(EXT4_I(inode)-i_state EXT4_STATE_NO_EXPAND)) {
+ /* We need extra buffer
On Jul 11, 2007 00:30 -0500, Jose R. Santos wrote:
On Tue, 10 Jul 2007 22:12:14 -0600
Andreas Dilger [EMAIL PROTECTED] wrote:
You might also want to test out placement of the journal in the middle
of the filesystem, the U. Wisconsin folks tested this in one of their
papers and showed some
On Jul 10, 2007 22:40 -0700, Andrew Morton wrote:
On Sun, 01 Jul 2007 03:38:18 -0400 Mingming Cao [EMAIL PROTECTED] wrote:
A EXT4_FEATURE_RO_COMPAT_DIR_NLINK flag has been added and it is set if
the subdir count for any directory crosses 65000.
Would I be correct in assuming that a later
Hi Andreas,
Trying to resize a mounted ext3 filesystem fails due to small journal size.
Background :
The filesystem was created with default values, except blocksize = 4K on
a LV partition. Later we tried extended the partition to +16M and tried
to resize the fs using resize2fs, while it was
On Tue, Jul 10, 2007 at 04:31:44PM -0700, Andrew Morton wrote:
On Sun, 01 Jul 2007 03:37:53 -0400
Mingming Cao [EMAIL PROTECTED] wrote:
Add a noversion mount option to disable inode version updates.
Why is this option being offered to our users? To reduce disk traffic,
like noatime?
On Wed, Jul 11, 2007 at 01:21:55PM +1000, Neil Brown wrote:
And just by-the-way, the server doesn't really have the option of not
sending the attribute. If i_version isn't defined, it has to fake
something using mtime, and hope that is good enough.
ctime, actually--the change attribute is
On Wed, 11 Jul 2007 07:01:08 -0600 Andreas Dilger [EMAIL PROTECTED] wrote:
- /* AKPM: buglet - add `i' to tmp! */
Damn. After, what, seven years, someone actually fixed it?
for (i = 0; i bh-b_size; i += 512) {
- journal_header_t *tmp =
On Wed, 11 Jul 2007 06:10:56 -0600 Andreas Dilger [EMAIL PROTECTED] wrote:
On Jul 10, 2007 16:32 -0700, Andrew Morton wrote:
err = ext4_reserve_inode_write(handle, inode, iloc);
+ if (EXT4_I(inode)-i_extra_isize
+ EXT4_SB(inode-i_sb)-s_want_extra_isize
+
On Wed, Jul 11, 2007 at 03:44:11AM -0600, Andreas Dilger wrote:
I've already found some kind of memory corruption in e2fsck as a result
of running this as a regular user. It segfaults in qsort() when freeing
memory. The image that causes this problem is attached, and it happens
with the
Set the journals JBD2_FEATURE_INCOMPAT_64BIT on devices with more
than 32bit block sizes during mount time. This ensure proper record
lenth when writing to the journal.
Signed-off-by: Jose R. Santos [EMAIL PROTECTED]
Signed-off-by: Andreas Dilger [EMAIL PROTECTED]
Signed-off-by: Mingming Cao
The patch titled
jbd2 commit: fix transaction dropping
has been added to the -mm tree. Its filename is
jbd2-commit-fix-transaction-dropping.patch
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See
The jbd2-debug file used to be located in /proc/sys/fs/jbd2-debug, but
create_proc_entry() does not do lookups on file names that are more that one
directory deep. This causes the entry creation to fail and hence, no proc
file is created.
Instead of fixing this on procfs might as well move the
On Wed, 2007-07-11 at 10:34 -0700, Andrew Morton wrote:
On Wed, 11 Jul 2007 06:10:56 -0600 Andreas Dilger [EMAIL PROTECTED] wrote:
On Jul 10, 2007 16:32 -0700, Andrew Morton wrote:
err = ext4_reserve_inode_write(handle, inode, iloc);
+ if (EXT4_I(inode)-i_extra_isize
On Wed, 2007-07-11 at 19:30 +0530, Suzuki wrote:
Hi Andreas,
Trying to resize a mounted ext3 filesystem fails due to small journal size.
A similar problem was discussed in an earlier thread JBD: ext2online
wants too many credits (744 256). The problem here is that the
maximum allowed
On Wed, Jul 11, 2007 at 09:28:06AM -0500, Dave Kleikamp wrote:
On Wed, 2007-07-11 at 15:05 +1000, Neil Brown wrote:
It just occurred to me:
If i_version is 64bit, then knfsd would need to be careful when
reading it on a 32bit host. What are the locking rules?
How does knfsd use
On Wed, Jul 11, 2007 at 12:30:04AM -0500, Jose R. Santos wrote:
i think in the spirit of the original META_BG option, Ted had wanted to
put all the bitmaps from EXT4_DESC_PER_BLOCK groups somewhere within the
metagroup. It would also be interesting to see if moving ALL of the
group
On Wed, Jul 11, 2007 at 12:30:04AM -0500, Jose R. Santos wrote:
Right now what I've done is allocate the bitmaps and inode tables at the
beginning of each group of 64 BG. Still need to work on fsck since just
removing the restriction on were the bitmaps and inode table are
located still gives
On Tue, 2007-07-10 at 23:20 -0700, Andrew Morton wrote:
On Sun, 01 Jul 2007 03:38:59 -0400 Mingming Cao [EMAIL PROTECTED] wrote:
From: Dmitry Monakhov [EMAIL PROTECTED]
Subject: ext4: extent macros cleanup
- Replace math equation to it's macro equivalent
s/it's/its/;)
Okay.
-
On Jul 11, 2007 19:30 +0530, Suzuki wrote:
Trying to resize a mounted ext3 filesystem fails due to small journal size.
Background :
The filesystem was created with default values, except blocksize = 4K on
a LV partition. Later we tried extended the partition to +16M and tried
to resize
Andreas Dilger wrote:
On Jul 11, 2007 19:30 +0530, Suzuki wrote:
Trying to resize a mounted ext3 filesystem fails due to small journal size.
Background :
The filesystem was created with default values, except blocksize = 4K on
a LV partition. Later we tried extended the partition to +16M
On Jul 11, 2007 13:43 -0400, Theodore Tso wrote:
Fix e2fsck segfault on very badly damaged filesystems
--- a/e2fsck/dirinfo.c
+++ b/e2fsck/dirinfo.c
@@ -126,7 +126,7 @@ void e2fsck_add_dir_info(e2fsck_t ctx, ext2_ino_t ino,
ext2_ino_t parent)
ctx-dir_info-size +=
I've got another one, but it isn't a show stopper I think.
If you format a filesystem with both resize_inode and meta_bg you get an
unfixable filesystem. The bad news is that it appears that running
e2fsck on the filesystem is actually _causing_ the corruption in this case
(trying to rebuild the
42 matches
Mail list logo
