EXT3-fs warning (device dm-0): ext3_dx_add_entry: Directory index full!
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
EXT3-fs warning (device dm-0): ext3_dx_add_entry: Directory index full!
I am running a ClarkConnect Community 4.2 gateway. This is a Redhat 2.26 kernel Linux system.
I get the error above error when I run "dmesg":
EXT3-fs warning (device dm-0): ext3_dx_add_entry: Directory index full!
I have run out of disk space on my /var mount point. This is a 10GB volume group.
I have extended the volume group and volume name to 25 GB and is now trying to resize the file system for the mail server to restore function to the file systems and mail server (postfix).
I am having serious problems running resize2fs as it indicates that the /var directory is busy and canot be unmounted.
The mount command show:
mounted partitions:
[root@Assurance mapper]# mount
/dev/sdb1 on / type ext3 (rw)
none on /proc type proc (rw)
none on /sys type sysfs (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
usbfs on /proc/bus/usb type usbfs (rw)
/dev/sda1 on /boot type ext3 (rw)
none on /dev/shm type tmpfs (rw)
/dev/sda2 on /home type ext3 (rw)
/dev/sdb2 on /usr type ext3 (rw)
/dev/mapper/VolGroup00-LogVol00 on /var type ext3 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
The following device is the one that needs to be resized:
/dev/mapper/VolGroup00-LogVol00 on /var type ext3 (rw)
Results of several commands ie. pvscan and dumpconfigure
lvm> pvscan
PV /dev/sdb3 VG VolGroup00 lvm2 [138.28 GB / 125.56 GB free]
PV /dev/sda3 VG VolGroup00 lvm2 [119.62 GB / 119.62 GB free]
Total: 2 [257.91 GB] / in use: 2 [257.91 GB] / in no VG: 0 [0 ]
fuser run with the -v switch shows:
[root@Assurance /]# fuser -v /var
USER PID ACCESS COMMAND
/var root kernel mount /var
when i run umount i get the following:
[root@Assurance ~]# umount /var -l
umount: /var: not mounted
[root@Assurance ~]#
but I get this when I run fsck /var
/var mount issues:
fsck.ext3: Device or resource busy while trying to open /dev/VolGroup00/LogVol00
Filesystem mounted or opened exclusively by another program?
Finally fuser shows the following:
[root@Assurance log]# fuser -kv /var
USER PID ACCESS COMMAND
/var root 4692 ..c.. locate
root 4693 ..c.. less
root 4727 ..c.. less
root kernel mount /var
No automatic removal. Please use umount /var
Does anyone have and idea what all this is saying or mean.
I have checked this forum for solutions but no one has a problem similar to this one.
I would appreciate any help or suggestions.
Thanks in advance.
cgreen6911
Last edited by cgreen6911; 03-28-2008 at 06:52 PM.
I am running a ClarkConnect Community 4.2 gateway. This is a Redhat 2.26 kernel Linux system.
I get the error above error when I run "dmesg":
EXT3-fs warning (device dm-0): ext3_dx_add_entry: Directory index full!
I have run out of disk space on my /var mount point. This is a 10GB volume group.
I have extended the volume group and volume name to 25 GB and is now trying to resize the file system for the mail server to restore function to the file systems and mail server (postfix).
I am having serious problems running resize2fs as it indicates that the /var directory is busy and canot be unmounted.
The mount command show:
mounted partitions:
[root@Assurance mapper]# mount
/dev/sdb1 on / type ext3 (rw)
none on /proc type proc (rw)
none on /sys type sysfs (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
usbfs on /proc/bus/usb type usbfs (rw)
/dev/sda1 on /boot type ext3 (rw)
none on /dev/shm type tmpfs (rw)
/dev/sda2 on /home type ext3 (rw)
/dev/sdb2 on /usr type ext3 (rw)
/dev/mapper/VolGroup00-LogVol00 on /var type ext3 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
The following device is the one that needs to be resized:
/dev/mapper/VolGroup00-LogVol00 on /var type ext3 (rw)
Results of several commands ie. pvscan and dumpconfigure
lvm> pvscan
PV /dev/sdb3 VG VolGroup00 lvm2 [138.28 GB / 125.56 GB free]
PV /dev/sda3 VG VolGroup00 lvm2 [119.62 GB / 119.62 GB free]
Total: 2 [257.91 GB] / in use: 2 [257.91 GB] / in no VG: 0 [0 ]
fuser run with the -v switch shows:
[root@Assurance /]# fuser -v /var
USER PID ACCESS COMMAND
/var root kernel mount /var
when i run umount i get the following:
[root@Assurance ~]# umount /var -l
umount: /var: not mounted
[root@Assurance ~]#
but I get this when I run fsck /var
/var mount issues:
fsck.ext3: Device or resource busy while trying to open /dev/VolGroup00/LogVol00
Filesystem mounted or opened exclusively by another program?
Finally fuser shows the following:
[root@Assurance log]# fuser -kv /var
USER PID ACCESS COMMAND
/var root 4692 ..c.. locate
root 4693 ..c.. less
root 4727 ..c.. less
root kernel mount /var
No automatic removal. Please use umount /var
Does anyone have and idea what all this is saying or mean.
I have checked this forum for solutions but no one has a problem similar to this one.
It may have more to do with the options used when formatting the ext3 filesystem than with the size of the partition. Try seeing if you have an "ext3" filesystem, or look for an ext3.txt file in the Kernel documentation.
Also see if you have 10s of thousands of empty files or empty directories on the filesystem that shouldn't be. When I used SuSE 10.1, something went wrong with the update system and there were tons of empty directories that were being created.
As you suggested I have looked into my systems for a lot of small files. i noticed that my
/var/cache/apt/archives folder have several GBs of rpm files from apt updates.
I am new to Linux. Is it ok to delete these archive files?
If so, I will be able to delete thse files and get quite a bit of space back until I can resolve how to resize my filesystem.
Is is ok to delete thse files or anr they needed for the system?
The error message was that the index (directory) was full and not the filesystem itself. I think it may be OK to delete these files. They will be re-downloaded if needed. You may want to investigate whether this indicates a problem, or if there is a cache limit you can set.
Be sure to look at hidden directories and files as well (in /var/cache). I think that is where kerry beagle and uncompressed man pages are cached as well.
EXT3-fs warning (device dm-0): ext3_dx_add_entry: Directory index full!
I have been chasing my tail on this issue for the last 48 hours.
I get this error when I run dmesg:
EXT3-fs warning (device dm-0): ext3_dx_add_entry: Directory index full!
I am not at all familiar with working with filesystems.
I know I need to unmount the filesystem before I can do anything to check the condition of the dir_index on the filesystem. However, I get the errors listed below:
[root@Assurance /]# umount /dev/mapper/VolGroup00-LogVol00
umount: /var: device is busy
umount: /var: device is busy
[root@Assurance /]# umount -l /dev/mapper/VolGroup00-LogVol00
[root@Assurance /]# e2fsck /dev/mapper/VolGroup00-LogVol00
e2fsck 1.39 (29-May-2006)
e2fsck: Device or resource busy while trying to open /dev/mapper/VolGroup00-LogVol00
Filesystem mounted or opened exclusively by another program?
How do you unmount a /dev/mapper raided filesystem?
How do you fix the, "EXT3-fs warning (device dm-0): ext3_dx_add_entry: Directory index full!" issue?
Any help or suggestions would be useful and appreciated.
Also searches on the web indicate this might be something to do with have a large number of files in one directory.
I assume you've got 10 gigs of old emails in a postfix queue .
If you need to unmount /var normally fuser -m /var will let you know whats running on it, course you fuser -k as you've mentioned too.
Running in single user mode if practical might be most beneficial. If you get desperate you can of course comment out /var in fstab and run in single user mode to the fsck the drive and/or resize2fs it.
Also bear in mind that running fsck on a filesystem with a directory containing an overwhelming number of files might end up just making your machine run out of ram, forcing you to reboot and/or corrupting the filesystem your trying to grow.
I will find a way to boot into single user mode. If that does not work, what is the risk to commenting out the /etc/fstab and removing /var to run fsck? I want to avoid corruption at any cost.
By the way, this is the results when I run Fuser -m /var. I get hundreds of processes using the /var filesystem. Not a simple taks to kill all of these processes.
I have deleted hundreds of these files so far but is still getting the same error below:
"EXT3-fs warning (device dm-0): ext3_dx_add_entry: Directory index full!"
Finally, when i run df on the /dev/mapper or raid drive, it shows that there is only 399K left on the filesystem. I believe that this is the source of my problem.
I have tried sveral ways to unmount this drive to run e2fsck on it but i get the error that the filesystem is busy.
when i go to single user mode iget the error:
e2fsck 1.39 (29-May-2006)
e2fsck: Device or resource busy while trying to open /dev/mapper/VolGroup00-LogVol00
Filesystem mounted or opened exclusively by another program?
I believe that if i can resize this filesystem that I will be able to resolve this issue.
What is the correct process for unmounting a raid or /dev/mapper filesystem?
However, when I run a df I get the following results:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sdb1 1003795 146643 806148 16% /
/dev/sda1 102711 7727 89765 8% /boot
none 777492 0 777492 0% /dev/shm
/dev/sda2 30226637 12368235 16322588 44% /home
/dev/sdb2 10078190 1537289 8028830 17% /usr /dev/mapper/VolGroup00-LogVol00
10318745 9566300 228174 98% /var
My /dev/mapper/VolGroup00-LogVol00 filesystem is at 98% of its capacity!
I believe that this is my issue.
See note from prior post for results of efforts to umount and do a fsck of this filesystem. I really have been chasing my tail on this issue!
This situation is complicated by the fact that I have SATA drives and my operating system has setup my filesystem with /dev/mapper!
I have not been able to figure out how to umount this device to resize the filesystem to add additional space.
Does the work to expand the file system have to be done offline?
Managing filesystems top this level is new to me, I do not have the experience at this time to develop a recover plan.
Does anyone have an idea how I should proceed assuming that this is a filesystem issue and not an inode issue?
I would appeciate any help or ideas, I have not had email for over a week and now my firewall needs to be rebooted twice a day just to keep the internet working.
Thanks in advance.
cgreen6911
Last edited by cgreen6911; 04-01-2008 at 02:32 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.