similar to: [PATCH] fstype: Fix ext4/ext4dev probing

Commit-ID: 52251e210c7a21068063fe16a3874903d3f1aa14 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=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

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

Add some semi-useful error message, as printing the failing dir or file seems not really advisable after that error. Signed-off-by: maximilian attems <max at stro.at> --- usr/utils/ln.c | 20 +++++++++++++++----- 1 files changed, 15 insertions(+), 5 deletions(-) diff --git a/usr/utils/ln.c b/usr/utils/ln.c index e826eb8..257b33f 100644 --- a/usr/utils/ln.c +++ b/usr/utils/ln.c @@ -9,7

hello hpa, rebased my branch, please pull latest git pull git://brane.itp.tuwien.ac.at/~mattems/klibc.git maks for the following shortlog maximilian attems (6): fstype: add squashfs v3 support reiser4_fs.h: add attribute packed to reiser4_master_sb fstype: add ext4 support .gitignore: add subdir specific entries usr/klibc/Kbuild: beautify klibc build fstype:

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

Make check_for_modules() more readable, just allways call continue on NULL return. That way the possible null dereference in strlen is no longer possible. This doesn't yet make it unsuck, but is a small step. Seen fixed too in blkid there with patch adding ko.gz support. Cc: Karel Zak <kzak at redhat.com> Signed-off-by: maximilian attems <max at stro.at> ---

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

Various coding style fixes checkpatch warns about. The goal is not to be 100% checkpatch compliant, but to have more consistent coding style. As this is a trivial patch serie, will land in 24 hours in klibc git, unless of course ml review hits a bugger. Checked with size(3) that the generated kinit, fstype, ipconfig and nfsmount are the same. maximilian attems (4): [klibc] ipconfig: reduce

I have released version 2.0.8. This is available in the git repository at: https://git.kernel.org/pub/scm/libs/klibc/klibc.git and as a tarball at: https://mirrors.kernel.org/pub/linux/libs/klibc/2.0/ New features: - Support for building with clang and lld, at least on x86 - Defined sysconf(), initially supporting only _SC_PAGE_SIZE - Defined clearerr() as extern - Defined stdio

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

tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost head: 9991b95cb712cdd9a40240bde6274d5415476fb5 commit: 860c7fa9d6d433011e82a4f7f896893e914ce4a9 [11/22] fw_cfg: write vmcoreinfo details config: i386-randconfig-a0-201804 (attached as .config) compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4 reproduce: git checkout 860c7fa9d6d433011e82a4f7f896893e914ce4a9 # save

I have accidently damaged the first block(s) of a btrfs partition and can''t mount it anymore. I can see that my data is still intact by running a command like: cat /dev/sda5 | hexdump -C | more Do any (experimental) tools exist which would allow me to recover the files? Thank you -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a

tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost head: 9991b95cb712cdd9a40240bde6274d5415476fb5 commit: 860c7fa9d6d433011e82a4f7f896893e914ce4a9 [11/22] fw_cfg: write vmcoreinfo details config: i386-randconfig-c0-02011330 (attached as .config) compiler: gcc-7 (Debian 7.2.0-12) 7.2.1 20171025 reproduce: git checkout 860c7fa9d6d433011e82a4f7f896893e914ce4a9

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>

Hello everyone, I''m totally new to Xen and trying to run it on some platforms (x86, x64) using SLES (that is what I have to use for reasons other than technical). Several machines on which I tried using Xen simply fails to run normally using Xen kernel: either network communication is not functioning at all despite proper configuration (that works on non-Xen kernel), or the kernel

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, I am running the glusterFS 3.4.1 NFS server. I have created a distributed volume on server 1 , and I am trying to mount the soft link contained in the volume as NFS from server 2 . but it is failing with the error " mount.nfs: an incorrect mount option was specified" Below is the volume in the server 1 that I am trying to export server 1 sh# gluster volume info all Volume

This patch adds support for the F2FS filesystem to fstype. Signed-off-by: Marc Dietrich <marvin24 at gmx.de> --- usr/kinit/fstype/f2fs_fs.h | 44 ++++++++++++++++++++++++++++++++++++++++++++ usr/kinit/fstype/fstype.c | 14 ++++++++++++++ 2 files changed, 58 insertions(+) create mode 100644 usr/kinit/fstype/f2fs_fs.h diff --git a/usr/kinit/fstype/f2fs_fs.h b/usr/kinit/fstype/f2fs_fs.h

This patch ports 5 new applications to the stubdom makefile structure for inclusion into stubdom domains. While these are required for vtpm-stubdom and vtpmmgrdom they could be used with other stubdom applications. -libgmp 4.3.2 -openssl 1.0.0a -polarssl 0.12.1 -berlios tpm_emulator 0.6.1 -vtpm_manager (from the tools directory) Signed off by: Matthew Fioravante