search for: ext4dev

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_COMP...

...=commit;h=52251e210c7a21068063fe16a3874903d3f1aa14 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Mon, 7 Oct 2019 20:39:46 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Tue, 8 Oct 2019 00:13:20 +0100 [klibc] fstype: Drop obsolete support for "ext4dev" This is obsolete since Linux 2.6.28, and it's now causing problems for people using compressed modules because we don't recognise the ext4 module with a .gz or .xz extension. Reported-by: Greg Edwards <gedwards at ddn.com> References: https://bugs.debian.org/932926 Signed-off-...

I made a filesystem (mke2fs -j) on a logical volume under kernel 2.6.20 on a 64-bit based system, and when I try to mount it, ext3 complains with EXT3-fs: dm-1: couldn't mount because of unsupported optional features (80). I first thought I just forgot to make the filesystem, so I remade it and the error is still present. I ran fsck on this freshly made filesystem, and it completed with

Hi, Recently I build a filesystem in a device using mkfs.ext4 but when I tried to mount the device show this error: ??? mount: unknown filesystem type 'ext4' But when I build the same device with mkfs.ext4dev I can mont the device without problem. My doubt is when Centos 5.4 is released if I will have a problem because the partition is ext4dev. Thanks, -- Daniel Bruno http://danielbruno.eti.br danielbruno at projetofedora.org

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 on vfstype arg maximilian a...

Hi, I was wondering what is the current status fro ext4 support in Centos. I've noticed that is marked as dev when I try to use it from the installer. Does anybody have a scary story to prevent using it? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20090902/7ba417df/attachment-0001.html>

...yscalls.mk +syscalls.nrs +typesize.bin +typesize.c commit cfbff10509b1ee6964339684e739d6f086e44b5e Author: maximilian attems <max at stro.at> Date: Sat Aug 11 12:34:01 2007 +0200 fstype: add ext4 support ext3_fs.h: add the new flags. one still need some oot e2fsprogs, but ext4dev is in linus ./misc/mke2fs -j /dev/mapper/nancy_vg1-ext4 mount /dev/mapper/nancy_vg1-ext4 /mnt -t ext4dev -o extents touch /mnt/oooo ./src/klibc/usr/kinit/fstype/static/fstype /dev/mapper/nancy_vg1-ext4 FSTYPE=ext4dev FSSIZE=314572800 will probably once get rena...

Listee's... I have a 5.5 box and I have formatted a partition as ext4 however I can't mount it, the mount command is telling me its an unknown file system type. fsck tells me the partition is a clean ext4 partition but I can't mount it. Some reasearch has lead me to believe the problem is that ext4 isn't enabled in the kernel by default in 5.5 (this was originally a 5.2 box that

ocfs2 currently uses the Journaled Block Device (JBD) for its journaling. This is a very stable and tested codebase. However, JBD is limited by architecture to 32bit block numbers. This means an ocfs2 filesystem is limited to 2^32 blocks. With a 4K blocksize, that's 16TB. People want larger volumes. Fortunately, there is now JBD2. JBD2 adds 64bit block number support and some other

Hi All, For those testing EXT4 I seem to have found an issue with anaconda where by if you specify EXT4 fstype in your kickstart file it will not install and complains that if needs another 250MB of disk space. I've tried with my kickstart set for 10G for root at ext3 and it works fine. 10,15 and 20GB with EXT4 all fail. BTW: can't put /boot on it either. Just a heads up for all.

Is 5.3 and ext4 going to be safe? I have seen a couple reports of data loss using ext4? Has this already been fixed? What does the list recommend? ext3/ ext4? Thought maybe today we would start seeing 5.3 showing up... Looking forward to it. Jerry

...(2): [klibc] dash: shell: Fix clang warnings about "string plus integer" [klibc] dash: output: Fix clang warnings about GNU old-style field designator Ben Hutchings (26): [klibc] 2.0.7 released, next version is 2.0.8 [klibc] fstype: Drop obsolete support for "ext4dev" [klibc] losetup: Fix char signedness mismatches with <linux/loop.h> [klibc] losetup: Delete fallbacks to LOOP_{GET,SET}_STATUS [klibc] losetup: Use LOOP_CTL_GET_FREE to find free device [klibc] ipconfig: Document support for DNS server addresses [klibc] ipc...

My application always needs to sync file data after writing. I don't want anything handing around in the kernel buffers. I am wondering what is the best method to accomplish this. 1. Do I use EXT2 and use fdatasync() or fsync()? 2. Do I use EXT2 and mount with the "sync" option? 3. Do I use EXT2 and use the O_DIRECT flag on open()? 4. Do I use EXT3 in full journaled mode,

Hi, I've recently benchmarked btrfs v0.11 & v0.12 against ext2, ext3, ext4, jfs, reiserfs and xfs. OS: Ubuntu Hardy Kernel: 2.6.24(-5-server) Hardware: --------- Fu-Si Primergy RX330 S1 * AMD Opteron 2210 1.8 GHz * 1 GB RAM * 3 x 73 GB, 3Gb/s, hot plug, 10k rpm, 3.5" SAS HDD * LSI RAID 128 MB Fu-Si Econel 200 * Intel Xeon 5110 * 512 MB RAM

...2 splash=silent showopts module /boot/initrd-2.6.27.19-5-xen I have following xen packages installed (on SLES 11 x64): xen-3.3.1_18546_12-3.1 enic-kmp-xen-0.0.1_2.6.27.19_5-10.6 oracleasm-kmp-xen-2.0.5_2.6.27.19_5-7.6 xen-doc-pdf-3.3.1_18546_12-3.1 iscsitarget-kmp-xen-0.4.15_2.6.27.19_5-94.6 ext4dev-kmp-xen-0_2.6.27.19_5-7.6 xen-doc-html-3.3.1_18546_12-3.1 xen-libs-3.3.1_18546_12-3.1 xen-kmp-default-3.3.1_18546_12_2.6.27.19_5-3.1 brocade-bfa-kmp-xen-1.1.0.2_2.6.27.19_5-6.6 xen-tools-3.3.1_18546_12-3.1 kernel-xen-2.6.27.19-5.1 kernel-xen-base-2.6.27.19-5.1 fnic-kmp-xen-1.0.0_2.6.27.19_5-9.11 xe...

On a selection of boxes, ntpd running in Xen Dom0 reproducibly exhibits extermely high noise/jitter. Switching back to -default, non-xen kernel ntpd runs with very low jitter/noise. Question -- how can I ''tame'' ntpd noise & jitter when running in Dom0? Is the problem a config issue, or a bug? Already reported this downstream; everybody''s "stumped".

On a selection of boxes, ntpd running in Xen Dom0 reproducibly exhibits extermely high noise/jitter. Switching back to -default, non-xen kernel ntpd runs with very low jitter/noise. Question -- how can I ''tame'' ntpd noise & jitter when running in Dom0? Is the problem a config issue, or a bug? Already reported this downstream; everybody''s "stumped".