From morty+redhat at frakir.org Fri Apr 2 22:08:59 2010 From: morty+redhat at frakir.org (Morty) Date: Fri, 2 Apr 2010 18:08:59 -0400 Subject: e2fsck: aborted Message-ID: <20100402220859.GA18666@red-sonja> I've got an FS at $WORK that's giving a whole lot of fsck errors. It starts like so: fsck 1.41.3 (12-Oct-2008) e2fsck 1.41.3 (12-Oct-2008) archive contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Running additional passes to resolve blocks claimed by more than one inode... Pass 1B: Rescanning for multiply-claimed blocks Multiply-claimed block(s) in inode 163841: 101019648 Multiply-claimed block(s) in inode 163842: 101019649 101019650 101019651 101019652 101019653 101019654 101019655 Multiply-claimed block(s) in inode 163843: 101019656 101019657 101019658 101019659 101019660 101019661 101019662 101019663 101019664 101019665 101019666 101019667 101019668 101019669 101019670 101019671 101019672 101019673 101019674 101019675 101019676 101019677 101019678 101019679 101019680 101019681 101019682 101019683 101019684 101019685 101019686 101019687 101019688 101019689 101019690 101019691 101019692 101019693 101019694 101019695 101019696 101019697 101019698 101019699 101019700 101019701 101019702 101019703 101019704 101019705 101019706 101019707 101019708 101019709 101019710 101019711 101019712 101019713 101019714 101019715 101019716 101019717 101019718 101019719 101019720 101019721 101019722 101019723 101019724 101019725 101019726 101019727 101019728 101019729 101019730 101019731 101019732 101019733 101019734 101019735 101019736 101019737 101019738 101019739 101019740 101019741 101019742 101019743 101019744 101019745 101019746 [snip] After a while of this, I get the following error: e2fsck: Can't allocate block element e2fsck: aborted Google says the error relates to process memory size required for large FSs. The FS here is a 1TB FS, created before I started using largefile and largefile4 for large FSs. When I mount it, some data seems to be lost. Anything I can do other than recover from backup? - Morty From lists at nerdbynature.de Fri Apr 16 03:50:22 2010 From: lists at nerdbynature.de (Christian Kujau) Date: Thu, 15 Apr 2010 20:50:22 -0700 (PDT) Subject: e2fsck: aborted In-Reply-To: <20100402220859.GA18666@red-sonja> References: <20100402220859.GA18666@red-sonja> Message-ID: A bit late, but.... On Fri, 2 Apr 2010 at 18:08, Morty wrote: > e2fsck: Can't allocate block element > e2fsck: aborted > > Google says the error relates to process memory size required for > large FSs. The FS here is a 1TB FS, created before I started using How many inodes are on this filesystem? See http://lkml.org/lkml/2003/2/7/95 for some estimates. Maybe adding more RAM/switching to 64bit (if not already done) might help. Christian. -- BOFH excuse #205: Quantum dynamics are affecting the transistors From krg9263 at gmail.com Sat Apr 17 19:58:13 2010 From: krg9263 at gmail.com (Kevin Gutch) Date: Sat, 17 Apr 2010 15:58:13 -0400 Subject: Deleted file marker Message-ID: Is there a marker to indicate a deleted file in EXT3 similar to FAT32's E5? Thanks Kevin -------------- next part -------------- An HTML attachment was scrubbed... URL: From bruno at wolff.to Sun Apr 18 16:09:57 2010 From: bruno at wolff.to (Bruno Wolff III) Date: Sun, 18 Apr 2010 11:09:57 -0500 Subject: Deleted file marker In-Reply-To: References: Message-ID: <20100418160957.GA29873@wolff.to> On Sat, Apr 17, 2010 at 15:58:13 -0400, Kevin Gutch wrote: > Is there a marker to indicate a deleted file in EXT3 similar to FAT32's E5? It is generally a good idea to ask questions at a higher level unless you are interested in exactly that information. One might guess based on your question that you are really interested in recovering deleted files and not the specific structure of ext3 file systems. If that is the case, then you might want to take a look at ext3grep, which is packaged for Fedora. From lakshmipathi.g at gmail.com Mon Apr 19 03:30:51 2010 From: lakshmipathi.g at gmail.com (Lakshmipathi.G) Date: Mon, 19 Apr 2010 09:00:51 +0530 Subject: Deleted file marker In-Reply-To: <20100418160957.GA29873@wolff.to> References: <20100418160957.GA29873@wolff.to> Message-ID: If you are interested in - how ext3 file system handles deleted files - ext3 doesnt have special indicator to represent deleted files. If you interested in recovery,then as Bruno suggested try Carlo woods "ext3grep" which uses journal to recover files. On Sun, Apr 18, 2010 at 9:39 PM, Bruno Wolff III wrote: > On Sat, Apr 17, 2010 at 15:58:13 -0400, > Kevin Gutch wrote: > > Is there a marker to indicate a deleted file in EXT3 similar to FAT32's > E5? > > It is generally a good idea to ask questions at a higher level unless you > are interested in exactly that information. > > One might guess based on your question that you are really interested in > recovering deleted files and not the specific structure of ext3 file > systems. > If that is the case, then you might want to take a look at ext3grep, which > is packaged for Fedora. > > _______________________________________________ > Ext3-users mailing list > Ext3-users at redhat.com > https://www.redhat.com/mailman/listinfo/ext3-users > -- ---- Cheers, Lakshmipathi.G FOSS Programmer. www.giis.co.in -------------- next part -------------- An HTML attachment was scrubbed... URL: From jeremy at rsise.anu.edu.au Tue Apr 13 02:03:58 2010 From: jeremy at rsise.anu.edu.au (Jeremy Dawson) Date: Tue, 13 Apr 2010 12:03:58 +1000 Subject: ext3 filesystems - changes ?? Message-ID: <4BC3D10E.1090806@rsise.anu.edu.au> I hope this is a suitable forum for this question. I have RedHat9 installed on one partition. I have just installed Ubuntu 9.10 on another partition. When I had a choice in the installation procedure, I chose ext3 (since I understood that the RedHat partitions are ext3). Now I can mount the RedHat9 partitions from ubuntu, but trying to mount the Ubuntu partitions from RedHat produces an uninformative error message. Why could this be ? Are there different variants of ext3 ? Thanks for any help Jeremy From rwheeler at redhat.com Wed Apr 21 20:54:24 2010 From: rwheeler at redhat.com (Ric Wheeler) Date: Wed, 21 Apr 2010 16:54:24 -0400 Subject: ext3 filesystems - changes ?? In-Reply-To: <4BC3D10E.1090806@rsise.anu.edu.au> References: <4BC3D10E.1090806@rsise.anu.edu.au> Message-ID: <4BCF6600.40203@redhat.com> On 04/12/2010 10:03 PM, Jeremy Dawson wrote: > > I hope this is a suitable forum for this question. > > I have RedHat9 installed on one partition. > > I have just installed Ubuntu 9.10 on another partition. When I had a > choice in the installation procedure, I chose ext3 (since I understood > that the RedHat partitions are ext3). > > Now I can mount the RedHat9 partitions from ubuntu, but trying to > mount the Ubuntu partitions from RedHat produces an uninformative > error message. > > Why could this be ? Are there different variants of ext3 ? > > Thanks for any help > > Jeremy > > You should probably try to use a much more recent distribution - that sounds quite ancient. Fedora12 for example will give you something familiar for a Red Hat user and more choices :-) ric From sandeen at redhat.com Wed Apr 21 21:30:54 2010 From: sandeen at redhat.com (Eric Sandeen) Date: Wed, 21 Apr 2010 16:30:54 -0500 Subject: ext3 filesystems - changes ?? In-Reply-To: <4BC3D10E.1090806@rsise.anu.edu.au> References: <4BC3D10E.1090806@rsise.anu.edu.au> Message-ID: <4BCF6E8E.7030908@redhat.com> On 04/12/2010 09:03 PM, Jeremy Dawson wrote: > > I hope this is a suitable forum for this question. > > I have RedHat9 installed on one partition. > > I have just installed Ubuntu 9.10 on another partition. When I had a > choice in the installation procedure, I chose ext3 (since I understood > that the RedHat partitions are ext3). > > Now I can mount the RedHat9 partitions from ubuntu, but trying to mount > the Ubuntu partitions from RedHat produces an uninformative error message. > > Why could this be ? Are there different variants of ext3 ? to some degree yes, there are some ext3 features which older kernels may not mount. dmesg likely tells you -something- about the problem - including the error message is always helpful, even if it's uninformative to you :) (the generic mount failure message is generally worthless, but the kernel should say something) -Eric > Thanks for any help > > Jeremy > > > _______________________________________________ > Ext3-users mailing list > Ext3-users at redhat.com > https://www.redhat.com/mailman/listinfo/ext3-users