Displaying 20 results from an estimated 13000 matches similar to: "ext4 and extremely slow filesystem traversal"
2007 Mar 29
3
tune2fs -l stale info
Hello,
I just noticed that 'tune2fs -l' did not returned a "lively" updated
information regarding the free inodes count (looks like it's always
correct after unmounting). It became suprising after an online resizing
operation, where the total inode count was immediatly updated (grown in
my case) but the free inode count was the same: one could deduce that
suddenly a lot of
2016 Aug 19
2
e2find: new ext2/3/4 tool for fast directory entry iterations
Hello ext users,
in a recurrent need to be able to traverse large filesystems (10-350M
inodes) backed by spindle-based RAID arrays, I tried several solutions
(like intercepting readdir and sorting by inode, playing with cache
hints, and such), to no avail.
Since I'm mostly facing ext3 and ext4 filesystems, I wrote a tool
based on libe2fs which replaces the 'find /' part by
2008 May 27
2
needs help, root inode gone after usb bus reset on sata disks
Hello everybody,
I am new to this list, so welcome everybody.
Last 2 week I had two harddisk crashes with my ext2 file system.
This is what sort of happed with both of the disk:
I pluged in my USB to SATA converter in my harddisk that has an ext2
filesystem. I mounted the partition, went to a directory that had a DVD
image. I mounted the dvd image in the same directory and started
watching the
2009 Dec 08
3
botched RAID, now e2fsck or what?
Hi all,
Somehow I managed to mess with a RAID array containing an ext3 partition.
Parenthesis, if it matters: I disconnected physically a drive while
the array was online. Next thing, I lost the right order of the drives
in the array. While trying to re-create it, I overwrote the raid
superblocks. Luckily, the array was RAID5 degraded, so whenever I
re-created it, it didn't go into sync;
2001 Oct 17
3
"ext2fs_check_if_mount: No such file or directory while determining whether" messages
Hi. I was using 2.4.10 with ext3 0.9.10 and thought it was
time to use -ac for the first time because 2.4.12-ac3
includes 0.9.12.
I don't know what I did to get the following messages, but in
my last boot I removed /etc/mtab (at runtime) and made it a
symlink to /proc/mounts. Not sure if a bad idea, but the only
problem until I rebooted was the need of losetup -d.
When I rebooted, all
2014 Aug 17
2
What uses these 50 GB?
Hello everybody,
first of all thank you the development of Ext2/3/4. It works like a
charm and makes it possible to base applications on it.
However, now I have the first time where I need more information to
understand the behaviour of a ext4 installation on a 480 GB harddisk.
It holds a database with a size of 355 GB, as said by
"du -m":
...
355263 /opt/ssd
However,
2014 Apr 18
3
Re: Many orphaned inodes after resize2fs
Hi,
it seems you got it right! I don't know if you read email I sent you before
posting to the mailing list, but I accidentally diagnosed the cause... :)
I've noticed that inodes fsck warned me about, at least ones that I
checked, all have all four timestamps latest in 2010...
The filesystem has maximum 1281998848 inodes, which is timestamp in august
2010. I don't know how it got
2005 Oct 19
1
EXT3 journalling issue
Hello,
I have 2 boxes with 1.5TB storage with ext3 fs, and the kernel is 2.6.11.8.
I'm using E2fsprogs 1.37 for FS creation. And, Filesystem revision #: 1
(dynamic)
There are 2 scenarios:
1. All SATA drives, RAID5
2. All PATA drives, RAID5 and wrapped in log volumes.
I'm having lots of issues with fsck. I did search, but somehow not getting
the right information.
needs_recovery
2014 Aug 17
0
Re: What uses these 50 GB?
On 8/17/14, 12:28 PM, Roland Olbricht wrote:
> Hello everybody,
>
> first of all thank you the development of Ext2/3/4. It works like a
> charm and makes it possible to base applications on it.
> However, "df" says:
>
> Filesystem 1K-blocks Used Available Use% Mounted on
> ...
> /dev/sdc 468346644 409888536 35015532 93% /opt/ssd
>
2006 Jan 30
1
df reports false size
On a customer's machine running SuSE 9.2, the size of the occupied space on
the harddisk is reported incorrectly by "df -h". After we noticed the
problem, I rebooted the machine and had it checked by "e2fsck" (check forced
with "tune2fs -C 40", we are not on location). Right after the reboot I
proceeded as follows, but I could not find any information about
2014 Apr 18
2
Many orphaned inodes after resize2fs
Hello,
yesterday I experienced following problem with my ext3 filesystem:
- I had ext3 filesystem of the size of a few TB with journal. I correctly
unmounted it and it was marked clean.
- I then ran fsck.etx3 -f on it and it did not find any problem.
- After increasing size of its LVM volume by 1.5 TB I resized the
filesystem by resize2fs lvm_volume and it finished without problem.
- But
2014 Sep 20
4
Possible bug in mkfs.ext3
I am reporting this on the advice of the Fedora Users Mailing List Member.
This the mailing list exchange outlining the problem with specifying -S
to mkfs,
and it's subsequent consequences when fsck is run.
I am reporting this per suggestions made to me on the Fedora Users
Mailing List.
The following is the mailing list exchange:
On 09/18/2014 07:01 PM, Robert Nichols wrote:
> On
2014 Aug 17
3
Re: What uses these 50 GB?
Hello Eric,
thank you for the quick reply and the explanations.
> dumpe2fs -h output might show us that.
Filesystem volume name: <none>
Last mounted on: /opt/ssd
Filesystem UUID: 75d6aae6-1746-4260-994b-148dfdb5af95
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index
filetype
2014 Apr 18
0
Re: Many orphaned inodes after resize2fs
On Fri, Apr 18, 2014 at 06:56:57PM +0200, Patrik Horn?k wrote:
>
> yesterday I experienced following problem with my ext3 filesystem:
>
> - I had ext3 filesystem of the size of a few TB with journal. I correctly
> unmounted it and it was marked clean.
>
> - I then ran fsck.etx3 -f on it and it did not find any problem.
>
> - After increasing size of its LVM volume by
2005 Feb 07
3
e2fsck errors after lvextend when trying to resize2fs
I found a thread that has almost the exact same symptoms as me, but didn't
seem to come to a resolution:
https://listman.redhat.com/archives/ext3-users/2004-December/msg00018.html
I have an LVM(2) array that I've just lvextend'd and want to resize2fs, but I
can't get through the e2fsck. I get these errors when fsck-ing:
Group 3125's inode table at 102400545 conflicts with
2014 Sep 20
0
Re: Possible bug in mkfs.ext3
On Sep 19, 2014, at 7:56 PM, jd1008 <jd1008 at gmail.com> wrote:
> I am reporting this on the advice of the Fedora Users Mailing List Member.
>
> This the mailing list exchange outlining the problem with specifying -S to mkfs, and it's subsequent consequences when fsck is run.
>
> I am reporting this per suggestions made to me on the Fedora Users Mailing List.
I would
2007 Sep 20
8
How are alternate superblocks repaired?
Hi,
Using dumpe2fs I have been able to determine that all of my alternate ext3 superblocks are corrupted (not clean), and only the primary superblock is valid, i.e. mount works and the ordered journal is applied. When the primary superblock gets flakey, i.e. the ext_attr Filesystem feature goes missing - not sure why this occurs. At this point, the mount does not apply the journal using the
2003 Jan 19
3
All data "gone," lost+found is left.
So you know, I don't know too much about file systems.
Here is what I did: I have two linux boxes. the first box had many
hardrives in it, but needed to be used in other ways. So I took 4
harddrives out of it and placed it in the other Linux box. I thought it
would be able to read these right away. (maybe this was my mistake?) I
could mount all of the drives in there. three of my
2005 Oct 31
2
ext3 + fs > 2Tbyte
Hi list
this is actually a problem on a debian system but I thought you might
be interested to hear of it and perhaps can offer some help.
I have a woody box (dell pe750, dual cpu) running a kernel from
backports.org (debian 'testing' packages built on a 'stable' box).
The kernel version is 2.6.7-1.backports.org.1.
This host is hooked up to an Apple Xserve RAID with a 2.3Tbyte
2007 Jan 10
3
Can't mount /home anymore
Hi!
I'm new to the list. I have a problem with mounting my home directory since
my PC crashed. I hope that I can get some help on this list as I don't know
much of ext3 myself.
The mount command for my /home gives me the following output:
# mount /dev/sda6 /mnt/tmp/
mount: wrong fs type, bad option, bad superblock on /dev/sda6,
missing codepage or other error
In some cases useful info