similar to: [PATCH] FSUUID for ext2 filesystem

As per ext4 specification: > In ext2, ext3, and ext4 (when the 64bit feature is not enabled), the > block group descriptor was only 32 bytes long and therefore ends at > bg_checksum. On an ext4 filesystem with the 64bit feature enabled, the > block group descriptor expands to at least the 64 bytes described below; > the size is stored in the superblock. Since block group

Hi, This branch contains the new ext4's inline data support which has been added recently to kernel 3.8. In addition to inline data support, there are other patches that remove trainling whitespaces and extra new lines in ext2fs code and the other adds an assert() macro to Syslinux core. I think it's worth mentioning that these changes were made against master branch.

[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 ---

Check if some pointers are not NULL due to read errors or other problems Signed-off-by: Frediano Ziglio <frediano.ziglio at citrix.com> --- core/fs/ext2/ext2.c | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/core/fs/ext2/ext2.c b/core/fs/ext2/ext2.c index bddde8d..8f0f2a4 100644 --- a/core/fs/ext2/ext2.c +++ b/core/fs/ext2/ext2.c @@ -139,6 +139,8 @@

A while back, I submitted a patch for PR kern/124621, which allows the mounting of an ext2(3) filesystem created with an inode size other than 128. The e2fsprogs' default is now 256, so file systems created on newer Linux distributions or with the port will not be mountable. I was hopeful this would get committed in time for 7.1-RELEASE (and 6.4-RELEASE), however the PR remains open. If

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

Filesystem UUID shows the partition we boot kernel from. The kernel parameter has format like FSUUID=DA1A-0B2E. The SYSAPPEND bit is 0x40000. Now the FAT only supports FSUUID. The patch is based on 67aaaeeb228. Signed-off-by: Serj Kalichev <serj.kalichev at gmail.com> --- com32/include/syslinux/sysappend.h | 1 + core/fs/btrfs/btrfs.c | 3 ++- core/fs/ext2/ext2.c

This is part of some patches to support sectors > 512. Currently I'm able to boot a Ubuntu kernel but seems that mboot is not working for some reason. This patch add a rdwr_bytes functions which remove the assumption in some places that sector is 512. This function is quite helpful if you are going to read/write a range of bytes to/from the stack without creating stack overflows for free.

hello hpa, please pull git pull git://brane.itp.tuwien.ac.at/~mattems/klibc.git maks for those changes: Kyle McMartin (1): klibc-utils: add dmesg maximilian attems (2): klibc comment fix fstype: add ocfs2 support with the following diffstat README | 2 usr/Kbuild | 2 usr/kinit/fstype/fstype.c | 15 +++++++

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:

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.

On 11/19/2013 04:30 AM, Serj Kalichev wrote: > Filesystem UUID shows the partition we boot kernel from. > The kernel parameter has format like FSUUID=DA1A-0B2E. > The SYSAPPEND bit is 0x40000. Now the FAT only supports FSUUID. > The patch is based on 67aaaeeb228. > > Signed-off-by: Serj Kalichev <serj.kalichev at gmail.com> Nice. It would be good to get a patch for ext2

New api mke2fs for full configuration of filesystem. Signed-off-by: Wanlong Gao <gaowanlong at cn.fujitsu.com> --- daemon/ext2.c | 452 +++++++++++++++++++++++++++++++++++++++++ generator/generator_actions.ml | 18 ++ gobject/Makefile.inc | 6 +- src/MAX_PROC_NR | 2 +- 4 files changed, 475 insertions(+), 3 deletions(-) diff --git

Searching threads back to 2013-07-01 (date of last message on thread), I've come up with the folloowing: -Needs review for inclusion: 12/26 Init cache once 11/27 efi PE header set 11/21 FSUUID for ext2 filesystem 10/15 Upgrade to Lua 5.2.2, add filesystem module and get_key binding (21) 09/23 com32: hdt: fix memory leak 10/3/12-12/16 4k sector support 10/18 MultiFS from MultiDisk 10/07 Lua

Dear all, I'm working on a shell script which is producing a bootable image file. It contains a populated MBR and a single file system (ext4) which again contains a debootstrabed debian stable distribution. Unfortunately, I'm experiencing problems with the bootability of the produced image. When selecting the installed system at the boot prompt, Syslinux responds with something like

X-Original-In-Reply-To: <CAD0Rxe=5uLCWQ+jfj1J6zepDzqx0vAiBREiwiKOih59MKgBDHg at mail.gmail.com> X-Previous: http://www.syslinux.org/archives/2015-January/023070.html On Mon, Jan 05, 2015 at 08:59:57PM -0500, Gene Cumm wrote: > On Sat, Jan 3, 2015 at 1:21 PM, Geert Stappers wrote: > > On Thu, Jan 01, 2015 at 09:48:16AM -0500, Gene Cumm wrote: > > >> I'm planning on

No material changes are made. --- Makefile | 10 +- convert.c => convert/convert.c | 803 +--------------------------------------- convert/convert.h | 76 ++++ convert/ext2.c | 791 +++++++++++++++++++++++++++++++++++++++ 4 files changed, 873 insertions(+), 807 deletions(-) rename convert.c => convert/convert.c (74%) create mode

On 01.07.2015 17:46, Ady via Syslinux wrote: > >> On 01.07.2015 12:10, Gene Cumm wrote: >>> On Wed, Jul 1, 2015 at 4:35 AM, poma <pomidorabelisima at gmail.com> wrote: >>>> >>>> To remind you once again. >>>> ISOLINUX >= 6.00 built with GCC >= 5.0.0 causes a broken boot. >>>> This relates specifically to the use of the

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

Before we start accessing a huge (> 16 TiB) OCFS2 volume, we need to confirm that its journal supports 64-bit offsets. So we need to check the journal's feature bits before recovering the journal. This is not possible with JBD2 at present, because the journal superblock (where the feature bits reside) is not loaded from disk until the journal is recovered. This patch loads the journal