similar to: [PATCH] ext3: Fix sparse -Wbitwise warnings.

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>

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

Hi all, ext3-0.0.5c is now up at: ftp.uk.linux.org:/pub/linux/sct/fs/jfs/ and ftp.*.kernel.org:/pub/linux/kernel/people/sct/ext3/ The most important part of this release is the e2fsprogs: e2fsck now supports the journal changes for metadata-only journaling. Ted, I've changed around the use of jfs* include files in e2fsprogs quite heavily here. In each build directory --- the lib/ext2fs

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.

Enhance fstype so it properly takes into account whether or not the ext4 and/or ext4dev filesystems are present, and properly handles the test_fs flag. The old code also has some really buggy checks --- for example, where it compared the set of supported ro_compat features against the incompat feature bitmask: (sb->s_feature_incompat & __cpu_to_le32(EXT3_FEATURE_RO_COMPAT_SUPP) I

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

We are having problems remounting an ext3 filesystem using an external journal device. The filesystem in question was working fine until the server was rebooted. This is what we see on dmesg when trying to mount: EXT3: failed to claim external journal device. The external journal lives on a LVM2 logical volume and it seems to be accessible ( we can dumpe2fs and see filesystem information).

hello hpa, nothing too exciting, again syncing latest Debian upload and subsequent patch emails. plus wanting to get the ext4dev in line for the Lenny release. :) please review. thanks -- maks please pull git pull git://git.debian.org/~maks/klibc.git maks for the changes: Arthur Loiret (1): Makefile (ARCH): Support sh4 as sh. David H?rdeman (1): [klibc] mount: allow multiple fs

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

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

If I have an image of a filesystem taken with dd, I can look at it with a hex editor and discover that an ext2/3 superblock is at offset 1024 and I can figure out a lot of info about it. I cannot figure out, however, how the superblock differs from ext2 in ext3. I can't tell them apart... the "magic number" is the same as well as the "revision" field. If I have such an

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

Hello. After reading some mails from mailing list archives and other sources, ext3 seems to having troubles in deleting files w/o destroying the data neccessary to undelete them. Ok, I know what journaling means, and in any way, the ext3 fs driver needs to keep track of which blocks have actually been marked as being free. But now my question: Who say, that this information must be stored in

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

Added two debugfs entries... one to dump o2hb livenodes and the other to dump osb. $ cat /sys/kernel/debug/ocfs2/BC4F4550BEA74F92BDCC746AAD2EC0BF/fs_state Device => Id: 8,65 Uuid: BC4F4550BEA74F92BDCC746AAD2EC0BF Gen: 0xA02024F2 Label: sunil-xattr Volume => State: 1 Flags: 0x0 Sizes => Block: 4096 Cluster: 4096 Features => Compat: 0x1 Incompat: 0x350 ROcompat: 0x1

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:

ext4 no longer requires a journal. Compare: http://git.kernel.org/?p=fs/ext2/e2fsprogs.git;a=commitdiff;h=a90f5391dda78f7bc4a8196a78355584ace0adf5 Signed-off-by: Colin Watson <cjwatson at ubuntu.com> --- usr/kinit/fstype/fstype.c | 8 -------- 1 files changed, 0 insertions(+), 8 deletions(-) diff --git a/usr/kinit/fstype/fstype.c b/usr/kinit/fstype/fstype.c index 69e0e30..bf63b1b

Hello! Sorry to burden you but I somehow made one application to run via wine, but now there is a trouble with shortkeys. It is a general purpose 3D and when performing a special dynamic extrusion task which requires ctrl + H keys makes wine window to minimize into the panel. Obviously application Has this short key assigned to what it has to, I checked my desktop short keys and dind't find

Back again, the included patch adds pci functions from com32/modules/pcitest.c to lua. Example: -- get device info pciinfo = pci.getinfo() -- get plain text device description pciids = pci.getidlist("/pci.ids") -- list all pci busses for bind,businfo in pairs(pciinfo) do print("Bus: " .. bind .. " Devices:") -- list all devices on bus for dind,device in

Hello, I am having two data set original and predicted. I want to dind QQ-plot fot it. I tried in following manner : >qq(original~predicted) and error was : Error in qq.formula(o ~ p) : y must have exactly 2 levels There is an option "qtype" which dosent make any difference. What is the correct way for plotting QQ-plot or am I missing something. -- Amar Kumar Nandan