search for: e2image

I have been looking at integrating the e2image tool into my nightly backup routines for my systems, to improve the odds that I can get data back if something disastrous happens to my file system. I have a couple of questions about this, though, to work out if this is actually worth doing. Is e2image worth running if the file system is online...

Hi, i have two twofold e2image related questions: 1) The man page mentions "cp (1)"'s --sparse=always option. I wonder if there are sparse aware tools which a) display the "real" amount of disk space occupied by a sparse file b) compress sparse files (other than compressing very...

Hi folks -- My machine is a RHEL 3 with 2.4 kernel installed - with some large ext3 filesystems on drives connected internally ( >200G) Now, When this system crashed (for eg:- a CPU panic /hardware error ) - e2fsck on this filesystem seems to be taking a long time to return thereby adding to the overall downtime of this system. could there be any workarounds for my issue? say for

I know there is no straightforward way to recover deleted files on an ext3 file system, but is there any way to recover from an accidental mke2fs? -- --------------------------------------------------------------- Paul Raines email: raines@nmr.mgh.harvard.edu MGH/MIT/HMS Athinoula A. Martinos Center for Biomedical Imaging 149 (2301) 13th Street tel:(617)-724-2369

...free inodes, 1720 used directories Group 1: block bitmap at 0, inode bitmap at 0, inode table at 3016944 2289 free blocks, 46 free inodes, 2290 used directories ... # tune2fs -O ^has_journal /dev/hda1 tune2fs 1.28 (31-Aug-2002) tune2fs: Invalid argument while reading journal inode # e2image -r /dev/hda1 - e2image 1.28 (31-Aug-2002) Illegal block number passed to ext2fs_mark_block_bitmap #1027802808 for in-use block map Illegal block number passed to ext2fs_mark_block_bitmap #1027802809 for in-use block map Illegal block number passed to ext2fs_mark_block_bitmap #1027802810 for in-use...

Hi, I've run many time e2fsck, but in a special dir ls tells me: ls: r?cksendung-wlan.dvi: No such file or directory ls: baf?g_r?ckmeldung.latex: No such file or directory ls: finpr?f.pdf: No such file or directory $ cat finpr?f.pdf cat: finpr?f.pdf: Datei oder Verzeichnis nicht gefunden I don't know what to do? How can I find the failure? If I cat the files with debugfs, I see the

I have seen this happen a number of times: Jun 13 13:58:16 n202 kernel: EXT3-fs error (device sda5): ext3_get_inode_block: bad inode number: 9 Jun 13 13:58:16 n202 kernel: Aborting journal on device sda5. Jun 13 13:58:16 n202 kernel: EXT3-fs error (device sda5): ext3_get_inode_block: bad inode number: 9 Jun 13 13:58:16 n202 last message repeated 6 times Jun 13 13:58:18 n202 kernel: ext3_abort

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 No-one out there who can give me any tips for this? (Then the space to do experiments will finally be used in other ways. And I hope this mail won't be consired to impolite...) On Mon, 6 Dec 2004 15:23:15 +0100 Milan Holz?pfel <lists at mjh.name> wrote: > Hello, > > I got an IDE-drive which decided to get broken. Part of

Recently I've encountered a problem, and now I would preciate any help about being able to undelete files. My /var filestructured is mounted at /dev/hdc1 Part of my /etc/mtab looks like this: /dev/hdc1 /var ext3 rw 0 0 I'm using the e2fsprogs-1.23-2 package currently installed with Redhat 7.2 So, could anyone give me a hint of how things could be done to find deleted inodes? I've

Hi all, I know this is the EXT3 list, and my problem is with an EXT2 filesys, but I cannot seem to find a more suitable list on this server, and I have seen a lot of knowledge go by on this list and in the archives, so I thought I'd give it a try anyway... Here goes nothing: I am in a terrible problem: My data disk on my Linux server has gone bad, with approx 18 GB of data on it, and I

Hi! I was testing 2.6.0-test5, but got lots of journal aborted errors. Then I Sysrq-s/u/b and wanted to boot 2.4.23-pre3 or 2.4.22, but ext3 error: cannot find root fs cannot mount because of unsupported optional feature (4) after trying to mount it with ext2 (rootfstype=ext2, not working) I rebooted again into 2.4.22, this time there was just severe fs corrpution, illegal blocks, inodes,

Hi all, On Mon, Jun 02, 2014 at 11:04:52PM +0200, Bodo Thiesen wrote: > > Keith is not the first one with problems of this class and he will > probably not be the last one. He later told us, that at first, mounting > the file system still worked. Is there any value in discussing this issue in keeping this broken filesystem available for debugging purposes? I would like at this

...lock back to that inode maybe I can get further. The only thing is, I haven't done this before. I'd love to have something like reiserfs's fsck that reads the entire partition and tries to reconstruct the meta-data, but alas AFAIK ext2/3 doesn't have anything like that. I have an e2image file from the fs (unfortunately after the corruption), that is ~4mb after bzip2 compression that I can send to anyone interested. ta, Mike

...ke a long time on those partitions. I don't see that I lost anything although the databases aren't coming up. Thoughts? similar experiences? I'd like to know what else I could do to both find the problem source and to make sure I lose as little as possible when recovering. I used e2image -r and ran the fsck on it to make sure I knew what it was going to do. But I don't know anything really about the problem area. What else would be a good thing to try? Dana Bourgeois

...card to the machine and put two of the drives on their own IDE chains. At least, that is the opinion of the 2.6.0-test3 kernel that I had on the machine. e2fsck doesn't agree with that, as it reports on errors at all when checking the drive, and marks it clean. So, is anyone interested in an e2image of the filesystem, or anything like that? I am happy to generate one, and make it available for download or push it somewhere, if that will help work out this problem. Otherwise, I plan on changing the underlying kernel some time quite soon to get my backup machine running stably (I hope) again....

Hi - We have an ext3 file system which is 3.5TB in size (on top of lvm). Free are 172049011 out of 854473728 4096K blocks, and 396540654 out of 427245568 inodes. This is using Scientific Linux 4.4 (a RHEL clone). The filesystem consists of multiple backups created with rsync using --link-dest, which hard links files which haven't been modified to the previous copy. There are several hundred

Hello: I've been using EXT3 for awhile with Slackware Linux. I setup a master drive and I've been cloning it to identical hard drives using a hardware cloning device. My new batch of hard drives are a different size, so I can't use the hardware cloner. Is there any way to move the drive to a new, larger drive short of re-installing everything from scratch to make a new master?

* "Theodore Ts'o" <tytso@mit.edu> hat geschrieben: Hi Theodore. > That being said, it's pretty clear that portions of the inode table > and block group descriptor was badly corrupted. [...] Keith is not the first one with problems of this class and he will probably not be the last one. He later told us, that at first, mounting the file system still worked. And that

I met a power fail all sub-folders an files in /home folder are disappear. and fsck continue to report error in the filesystem. however, I can see any files and folder in debugfs and can rdump them to another folder and format ... and reinstall so bad!!! Question: Can I have a simple way to recover the data without reinstall and format Thanks Mike Lee

Hi, hoping that someone on this list can help me here is the Problem. After a crash it seems the journal could not be recovered. This is what mount gives: root@wuehlkiste:# mount -t ext3 /dev/hdb2 /mnt mount: wrong fs type, bad option, bad superblock on /dev/hdb2, or too many mounted file systems and this is the corresponding logfile-entry: Nov 27 11:16:13 wuehlkiste kernel: attempt to