similar to: When is a block free?

Chris, Perhaps you need to perform some write_conf like command. I''m not sure if this is needed in 1.6 or not. Shane ----- Original Message ----- From: lustre-discuss-bounces at lists.lustre.org <lustre-discuss-bounces at lists.lustre.org> To: lustre-discuss <lustre-discuss at lists.lustre.org> Sent: Fri Mar 07 12:03:17 2008 Subject: Re: [Lustre-discuss] Multihomed

I used ddrescue to copy /dev/md1 to a disk of sufficient size, and re-ran e2fsck, and still get the error message that there's no root file system (I've tried most every superblock): # fsck -y -b 7962624 /dev/sdf fsck 1.36 (05-Feb-2005) e2fsck 1.36 (05-Feb-2005) Superblock has a bad ext3 journal (inode 8). Clear? yes *** ext3 journal has been deleted - filesystem is now ext2 only ***

Hi there, I'm new to ext3, so I hope you won't find my question to be stupid. I also hope this isn't the 1,000,000th time someone posts it. My problem is the following: I converted my ext2 systems to ext3 using tune2fs -j /dev/sda2 (or 5 for my /home, 2 is my root) Then I modified fstab and put ext3 for each. After a reboot, the mount command says they are mounted as ext3. But when I

Hey, I've a problem with an ext3 filesystem and don't know how to fix it or find the failure :( The Hardware: Tyan mainboard, AMD Athlon CPU, ARECA ARC-1120 RaidController Raid5 with 400GB Seagate HD's, 756 MB Ram, other harddisks for system, network and avm isdn controller. Couse of the filesystem problems I run memtest and found one bad memory module which I replaced yet. The

I'm stuck on a problem with rsync... We've got a chrooted shell with rsync and all the needed libs inside (and not much else). We're using rsync over ssh to send the files into this chrooted session. The rsync binary in the chrooted session is SUID root so that it can create the files with the correct UID/GID. When the following is run, it creates all the files as root.staff, not

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.

Hi Stephen, I'm one of developers of SnapFS, which based on Ext3. I got Assertion failure from SnapFS, at ext3_new_block() in fs/ext3/balloc.c: J_ASSERT (!test_and_set_bit(BH_Alloced, &bh->b_state)) If J_ASSERT is only use as debug, why it will modify data? I found the 'BH_Alloced' flag only occures at two place: one is balloc.c as above, the other is at journal_forget() in

I recently came across an enormous cluster of x86 clone machines running fedora core 1 (2.4.24) which have typically all intel or amd have VIA IDE chipsets. They frequently experience corrupted journals rendering the ext3 partition in read-only mode. More important than recovering the filesystem, I am interested in finding the root of the problem. The common hardware that all of these

hi all, I installed v3.2 from source and now dom0 is booting well. But when I tried to start domU it shows the following error message and seems hanging. EXT3-fs: mounted filesystem with ordered data mode. EXT3-fs warning: mounting unchecked fs, running e2fsck is recommended EXT3 FS on hda1, internal journal device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@redhat.com

We have several large ext3 file system partitions. One of them sets itself to read-only after getting journel problems. I understand that's a good thing, but obviously I need to correct the problem so that it will stop locking itself. Here are some details; OS is Redhat EL4 x86_64 running on a SunFire v40z, kernel is 2.6.9-42.0.2.ELsmp. The disk storage in question is external, via

I have a damaged Ext3 filesystem which fsck has not been able to recover. If I try to mount it, I get a message like this in dmesg: EXT3-fs error (device sda1): ext3_free_blocks_sb: bit already cleared for block 2370866 If I try fsck on it, I get a series of messages like this: Inode bitmap for group 0 is not in group. (block 0) Relocate<y>? Up to group 95. Some say

[Re-sending to the ext3 list, with minor edits] I'm in the process of fixing errors generated by the Coverity tool on the Linux kernel, and I would like your comment on a set of problems reported in ext3. The main issue reported is not checking the return code of ext3_journal_get_write_access() in various places. I would like to know if there should be error handling in these cases. The

Hello anybody, I have a Suse 7.2 Linux with Kernel 2.4.9, which is compiled by myself, and is running stable. Now I try to patch my sourcecode in the way you write on your homepage. But thier are two Proglems: 1. When I download the the file "ext3-2.4-0.9.6-249.gz" with my Windows, I get no packedfile, I get a Textfile?! -so gunzip would not work. 2. never the less, I tried to patch

Dear list, This is the V4 of the trim support for xen-blkfront/blkback, Now we move BLKIF_OP_TRIM to BLKIF_OP_DISCARD, and dropped all "trim" stuffs in the patches, and use "discard" instead. Also we updated the helpers of blkif_x86_{32|64}_request or we will meet problems using a non-native protocol. And this patch has been tested with both SSD and raw file, with SSD we will

My manual patching of the rejects in checkpoint.c didn''t work out; a delete of 10,000 files caused a panic (in any ext fs, not just Lustre). In the new checkpoint.c, two routines expected by the patch no longer exist: __cleanup_transaction and __flush_buffer. I can avoid the panic if I omit (don''t try to manually patch) the following: Index: linux-2.6.9/fs/jbd/checkpoint.c

Setting mbox_min_index_size above zero and accessing a small mbox triggers the panic in index_storage_mailbox_init() at dovecot-1.0.rc25/src/lib-storage/index/index-storage.c:368 dovecot: Mar 03 01:28:03 Error: IMAP(user): in-memory index creation failed. dovecot: Mar 03 01:28:03 Error: IMAP(user): Raw backtrace: imap [0x80b52c4] -> imap [0x80b4d59] ->

This was a request from the systemd guys. They need a quick and easy way to get all devices attached to a Btrfs filesystem in order to check if any of the disks are SSD for...something, I didn''t ask :). I''ve tested this with the btrfs-progs patch that accompanies this patch. Thanks, Signed-off-by: Josef Bacik <josef@redhat.com> --- fs/btrfs/ioctl.c | 64

On 06/27/2011 07:46 AM, NeilBrown wrote: > On Thu, 23 Jun 2011 12:53:37 +0200 Nico Schottelius > <nico-lkml-20110623@schottelius.org> wrote: > >> Good morning devs, >> >> I''m wondering whether the raid- and volume-management-builtin of btrfs is >> actually a sane idea or not. >> Currently we do have md/device-mapper support for raid >>

Lo, Is there already a patch out for latest 2.4.6-ac release? I'm pretty sure that the ext3 patch -ac2 can not be applied on this release. Bye. -- the trees the birds the air the grass the water the flies the trees

Hi, Can anyone guide me in building the lustre using pre-packaged lustre release.I''m using Ubuntu 7.10 I want to build lustre using RHEL2.6 rpms available on my system.I''m referring how_to in wiki. but in that no detailed step by step procedure is given for building lustre using pre-packed release. I''m in need of this. Thanks and Regards, Ashok Bharat -----Original