From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Cc: findutils-patches@gnu.org
Subject: Re: stat(2) returning device ID not existing in mountinfo
Date: Fri, 17 Feb 2017 08:13:26 +0000 (UTC) [thread overview]
Message-ID: <pan$f1d62$6c5d9aea$6878f47$b58d3485@cox.net> (raw)
In-Reply-To: 925b4337-2de3-32fc-624f-ed67dd0eb8f2@libero.it
Goffredo Baroncelli posted on Wed, 15 Feb 2017 19:25:57 +0100 as
excerpted:
> (Resended because I don saw it in the mailing lists)
>
> -----
> Hi,
>
> I want to highlight this bug another time.
>
> I encountered this bug, when I was looking to a problem with find. I my
> machine find took an huge quantity of memory (up to 3GB) when used by
> updatedb.
FWIW, I saw it (via news.gmane.org list2news service) here. It's well
over my head, tho, so I didn't reply, but I found it interesting.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
prev parent reply other threads:[~2017-02-17 8:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 20:28 stat(2) returning device ID not existing in mountinfo Tomasz Sterna
2016-09-20 13:15 ` Jeff Mahoney
2017-02-13 19:21 ` Goffredo Baroncelli
2017-02-15 18:25 ` Goffredo Baroncelli
2017-02-17 8:13 ` Duncan [this message]
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='pan$f1d62$6c5d9aea$6878f47$b58d3485@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=findutils-patches@gnu.org \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).