search for: e2images

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 and in use, under the 2.6 series kernels, as part of

...than compressing very thightly several GiB of zeros) 2) "E2fsck, mke2fs, etc. will now reliably notice when image files are mounted using the loopback interface. (Addresses Sourceforge bug #619119)" (quoted from RELEASE-NOTES.gz) a) Is e2fsck now able to use (raw) e2images while repairing ext2 file systems? b) Is this also useful for ext3 file systems? Thanks for developing e2-tools and for the the great support in this list, Gregor -- echo '16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D3F204445524F42snlbxq'|dc

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

I just came back after being out for the evening. Apparently there was a power failure long enough to discharge the UPS completely on my Linux box. After powering back up, I received notice that the / filesystem needed "manual fsck"ing. I booted off CD and attempted to fsck. Unfortunately, everything I've tried has proved futile and I'm _desperate_ for some help. I've

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

Hi, I sent a message to linux-kernel that describes exactly what I did to thourally fsck up my ext3, but now I'm trying to see if I can recover more than the ext3 kernel driver will let me get to... http://marc.theaimsgroup.com/?l=linux-kernel&m=106745677408810&w=2 Now that you've read that, and you haven't given up hope (stubbornly like me), then I'd like to know what I

I fsck'd it and it seems to be in pretty good shape. This is 2.4.18 - RH9. This machine can't handle file system problems. It has to stay RH9 but I could back out the journalling. The machine is only 3 months old. I don't think it's a hardware issue. No error messages and the symptom (aside from being unusable) was I/O error seeking <different blocks>. The fsck

I have a bit of a problem with the machine I use at home for backups. The main partition the backups reside on is a 4 disk RAID-5, totaling around 240GB. This has had some sort of corruption inflicted on it, in the content of the (at least) one directory, where there are now corrupted directory entries. This happened after I added an additional SiS PCI IDE controller card to the machine and put

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