mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Udo van den Heuvel <udovdh@xs4all.nl>
To: Hugh Dickins <hugh@veritas.com>
Cc: linux-kernel@vger.kernel.org,
	Folkert van Heusden <folkert@vanheusden.com>
Subject: Re: 2.6.28.2 kernel bug
Date: Sun, 22 Mar 2009 06:52:23 +0100	[thread overview]
Message-ID: <49C5D217.2010201@xs4all.nl> (raw)
In-Reply-To: <Pine.LNX.4.64.0903212014380.15606@blonde.anvils>

Hugh Dickins wrote:
> This would become more interesting if you are able to reproduce it,

Just restarted the find command again, crashed after about 7 hours, this 
time with just one line in messages, about the bad page state for `find` 
again.

> or something like it - is that massive removal of files something
> you often do without a problem, or was this new?  What does your
> find/rm command line look like?  I'm wondering if we have a bug
> with exceptionally long arg lists.

I ran a find to get rid of ~2.5M files in 
~/.beagle/Indexes/Thunderbird/ToIndex which shouldn't have been there:
find ToIndex -type f -exec rm -f {} \;
This find runs pretty slowish.

The 2nd time I ran a sync severy 123 seconds to avoid big troubles in 
case of a crash.

Now I just made a list of all files and have a small shell script delete 
the files one by one.


I seldomly have these amounts of files to delete.
I never have this specific problem logged. (as far as I recall for this box)
It is typical that `find` triggers it and not cc1, Xorg etc.

  reply	other threads:[~2009-03-22  5:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-21 17:52 Udo van den Heuvel
2009-03-21 18:20 ` Udo van den Heuvel
2009-03-21 18:31 ` Alexey Dobriyan
2009-03-21 18:30   ` Udo van den Heuvel
2009-03-21 18:44     ` Alexey Dobriyan
2009-03-21 18:50       ` Udo van den Heuvel
2009-03-21 21:10 ` Hugh Dickins
2009-03-22  5:52   ` Udo van den Heuvel [this message]
2009-03-22 13:55     ` Hugh Dickins

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=49C5D217.2010201@xs4all.nl \
    --to=udovdh@xs4all.nl \
    --cc=folkert@vanheusden.com \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®