From: "Stephen D. Williams" <sdw@lig.net>
To: reiserfs-list@namesys.com
Subject: Very very slow rm/unlink of large sparse files
Date: Sun, 15 Feb 2004 22:29:35 -0500 [thread overview]
Message-ID: <4030391F.5080204@lig.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1868 bytes --]
Linux kernel 2.4.21-99 (SuSe 9 Pro kernel), and also experienced with 2.6.1.
When deleting a large file (4-10GB), at least somewhat sparse (created
completely sparse and filled in as a reiserfs filesystem under
user-mode-linux), the filesystem layer spends a very very long time, on
the order of several hours per GB, with constant disk activity trying to
delete the file. If the system is rebooted, the partial unlink is
continued at the same very very slow speed. A read-only mount works
just fine.
This is has happened several times as I have reinstalled and reoriented
systems. The filesystems are 40-500GB and are running on top of RAID
0,1, or 5 (ReiserFS->RAID 0, 1, or 5), sometimes with LVM
(ReiserFS->LVM->RAID 1). It seems completely repeatable and
consistent. I have been waiting about 24 hours for an unlink of a 9.9GB
file, formatted as ReiserFS and mostly filled with data. The filesystem
involved is accessible, but very very slowly. An ls of a small
directory takes at least 30 minutes. The system has 2GB ram and has at
least half of that free in buffers and cache. System load is over 8
because of things waiting for disk I/O, but CPU is 1% user and 3%
system. The disk LED is flashing at about 50% load, constant activity.
dd if=/dev/zero of=u.img bs=1 count=1 seek=$((1024 * 1024 * 4300))
mkfs.reiserfs -f u.img
mount -o loop u.img /mnt
cp -r /etc /mnt # I'm not sure how much data needs to be present, if
any, to exacerbate the problem.
umount /mnt
rm -f u.img
Is this a known problem? Has it been fixed in recent versions? Is
there a way to avoid practically (but not completely) locking up a
filesystem for many hours or days just to delete a file?
sdw
--
swilliams@hpti.com http://www.hpti.com Personal: sdw@lig.net http://sdw.st
Stephen D. Williams 703-724-0118W 703-995-0407Fax 20147-4622 AIM: sdw
next reply other threads:[~2004-02-16 3:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-16 3:29 Stephen D. Williams [this message]
2004-02-16 13:32 ` Very very slow rm/unlink of large sparse files Dieter Nützel
2004-02-16 13:42 ` Chris Mason
2004-02-16 14:06 ` Dieter Nützel
2004-02-16 14:29 ` Chris Mason
2004-02-16 15:49 ` Dieter Nützel
2004-02-16 15:59 ` Chris Mason
2004-02-16 18:55 ` Dieter Nützel
2004-02-16 15:22 ` Hans Reiser
2004-02-16 15:30 ` Dieter Nützel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4030391F.5080204@lig.net \
--to=sdw@lig.net \
--cc=reiserfs-list@namesys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.