similar to: ext3-0.0.5c released

Has anyone tried LFS (ie >2G files support) and Ext3 together? Are there good reasons why this should/should not work? I see the RH enterprise kernel patch set specifically does not attempt both lfs and ext3, but the lfs patches themselves touch some reasonably localised parts of ext2, so I would hope (without having dived in there to test), that the ext3 changes would mirror that

Signed-off-by: Alexey Dobriyan <adobriyan at mail.ru> --- fs/ext3/resize.c | 20 ++++++++++---------- fs/ext3/super.c | 8 ++++---- include/linux/ext3_fs.h | 2 +- 3 files changed, 15 insertions(+), 15 deletions(-) Index: linux-warnings/include/linux/ext3_fs.h =================================================================== ---

Hello, I just noticed that 'tune2fs -l' did not returned a "lively" updated information regarding the free inodes count (looks like it's always correct after unmounting). It became suprising after an online resizing operation, where the total inode count was immediatly updated (grown in my case) but the free inode count was the same: one could deduce that suddenly a lot of

Can anyone tell me the history of CONFIG_EXT{2,3}_CHECK? There is code for a "check" option for mount if these options are enabled, but there's no way to enable them. TIA Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said.

An embedded and charset-unspecified text was scrubbed... Name: sparse-fs_ext3_resize.patch URL: <http://listman.redhat.com/archives/ext3-users/attachments/20050620/8e33ffa8/attachment.ksh>

ext2 & ext3 lists, Attatched is a patch that allows ext2 and ext3 to link correctly when the kernel is configured with a large NR_CPUS. We do have an immediate need for this patch. Any opinions on this? The per-cpu lists are causing the kmalloc to fail due to allocating more than the max. thanks mh -- Martin Hicks Wild Open Source Inc. mort@wildopensource.com

hello hpa, nothing particular stands out, just syncing with latest Debian upload and subsequent patch emails. please review merge or nack. thanks :) maks git pull git://git.debian.org/~maks/klibc.git maks for the changes: Aaron Griffin (1): [klibc] kinit: skip md assembly if mdX exists Colin Watson (1): [klibc] mount/umount FUSE support Harald Jenny (1): [klibc] fstype:

This patch fixes the data loss which can occur when unmounting a data=journal ext3 filesystem. The core problem is that the VFS doesn't tell the filesystem enough about what is happening. ext3 _needs_ to know the difference between regular memory-cleansing writeback and sync-for-data-integrity purposes. (These two operations are really quite distinct, and the kernel has got it wrong for

[please note that I'm not subscribed to the list] Hi again, this patch adds support for the NILFS2 (http://www.nilfs.org/) filesystem to fstype (on top of 1.5.7 from the debian package). Please let me know what you think. (please note that I'm not affiliated to nilfs in any way). diff -Nur klibc-1.5.7.orig/usr/kinit/fstype/fstype.c klibc-1.5.7/usr/kinit/fstype/fstype.c ---

Hello. I found bugs on error handlings in the functions arround the ext3 file system, which cause inadequate completions of synchronous write I/O operations when disk I/O failures occur. Both 2.4 and 2.6 have this problem. I carried out following experiment: 1. Mount a ext3 file system on a SCSI disk with ordered mode. 2. Open a file on the file system with O_SYNC|O_RDWR|O_TRUNC|O_CREAT

The patch below contains the following cleanups: - make some needlessly global code static - super.c: remove the unused global function ext3_panic Please comment ib whether this patch is correct or conflicts with pending changes. diffstat output: fs/ext3/balloc.c | 2 fs/ext3/dir.c | 2 fs/ext3/inode.c | 4 fs/ext3/resize.c | 4

Hi, i am having problems converting the rootfs - I created a journal and booted with "rw rootflags=journal=<inode>" - Before i changes the fstab and put the WIP fsck to /sbin/fsck.ext3. The kernel seems to mount the filesystem ok and then the bootup scripts (debian potato) try to fsck the rootfs which leads to e2fsck 1.20-WIP, 17-Jan-2001 for EXT2 FS 0.5b, 95/08/09 JFS DEBUG:

Hi, ext3-0.0.5d.tar.gz is now up on ftp.uk.linux.org:/pub/linux/sct/fs/jfs/ and ftp.*.kernel.org:/pub/linux/kernel/people/sct/ext3/ as patches against 2.2.18. This only contains the kernel bits: we're in the process of syncing up on some e2fsprogs so I'll do another release shortly once we've got all of the pending changes for the user-mode tools assembled. This release is mostly

kfree() handles NULL pointers fine - checking is redundant. Signed-off-by: Jesper Juhl <juhl-lkml at dif.dk> --- linux-2.6.12-rc1-mm3-orig/fs/ext3/acl.c 2005-03-02 08:37:55.000000000 +0100 +++ linux-2.6.12-rc1-mm3/fs/ext3/acl.c 2005-03-25 22:41:41.000000000 +0100 @@ -197,8 +197,7 @@ ext3_get_acl(struct inode *inode, int ty acl = NULL; else acl = ERR_PTR(retval); - if (value) -

Hi, I've seen a problem where on recovery after a crash the orphan cleanup code clears the read_only bit and does not reset it. This causes the the fsck to drop to the "fix filesystem" prompt simply because the root filesystem is now mounted rw. It looks like this: Creating rootdevice Mounting rootfilesystem EXT3-fs: INFO: recovery required on readonly filesystem. EXT3-fs:

Hi In ext3_get_parent(), quick string (struct qstr) can do the job, in place of declaring a dentry on stack. Following patch does this and saves few bytes on kernel stack. Thanks, Maneesh namei.c | 69 ++++++++++++++++++++++++++++++---------------------------------- 1 files changed, 33 insertions(+), 36 deletions(-) diff -urN linux-2.5.58-base/fs/ext3/namei.c

Doing some debugging of my kernel build with ext3 and noticed something interesting. At the bottom of the rootflags options processing loop there is a return failure if there was an option that ext3 did not know about. Should this be the behaviour? Would it not be better to ignore options not recognized? Surely, some day, some other filesystem is going to want to use rootflags to have one of