similar to: How can I read superblock(ext2, ext3)'s information?

While untar''ing an image to an sd card via a reader, I got the following bug. The system also has a btrfs root, and a whole swath of processes went into uninterruptable sleep. I was able to poke around via ssh and sysrq, and already had netconsole set up to capture the bug. Root fs is on /dev/sdi1, and /dev/sdj2 is the card reader which was the target of the untar. [29571.448889] sd

Is there a way of checking an XFS filesystem for clean/dirty status while mounted? One of the checks we've long performed is an FS-level error check. This is *not a full-on fsck*, this is "asking the file system if it noted any problems". This is done while the file system is mounted and "hot". For example, here's how we'd check an ext* partition: # debugfs

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

My CentOS 5.4 box has a single HBA card with 2 ports connected to my Storage. 2 Luns are assigned to my HBA card. Under /dev instead of seeing 4 devices I can see 12 devices from sdb to sdm. I am using qlogic driver that is bulitin to the OS. Has any one seen this kind of situation? Paras -------------- next part -------------- An HTML attachment was scrubbed... URL:

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:

Hi I'm experiencing some problems on a harddisk (it has crashed for no known reason), and in pursuit of getting some of the data out of the disk I'm learning to use the e2fs progs package. Origianlly I used version 1.38, but after experiencing segfaults in e2fsck -which now is solved, I upgraded to 1.39, but now I have hit another problem (on another partition): The partition was

xfs_is_valid_magicnum is not actually a generic function that checks for magic numbers, instead it checks only for superblock's one. Signed-off-by: Paulo Alcantara <pcacjr at zytor.com> --- core/fs/xfs/xfs.c | 13 +++++-------- core/fs/xfs/xfs.h | 19 ++++++++++--------- 2 files changed, 15 insertions(+), 17 deletions(-) diff --git a/core/fs/xfs/xfs.c b/core/fs/xfs/xfs.c index

Hi, The following patches add support for ext4 and btrfs to PV-GRUB. These patches are taken nearly verbatim from those provided by Fedora and Gentoo. We''ve been using these patches for the PV-GRUB images available in EC2 for some time now with no problems. Changes from v1: - Makefile has been changed to check the exit code from patch - The btrfs patch has been rebased to apply

This pull request contains the XFS filesystem driver for Syslinux. Due to historical reasons (SGI IRIX's design of disk layouts), the first sector in the primary AG on XFS filesystems contains the superblock, which is a problem with BIOSes, since VBRs must be loaded up from the first sector of the active partition. Thus, we needed to handle this issue by putting the Syslinux bootsector