From: Sander <sander@humilis.net>
To: "Yan, Zheng " <yanzheng@21cn.com>
Cc: Johannes Hirte <johannes.hirte@fem.tu-ilmenau.de>,
linux-btrfs@vger.kernel.org, Chris Mason <chris.mason@oracle.com>
Subject: Re: Still ENOSPC problems with 2.6.35-rc3
Date: Thu, 17 Jun 2010 13:41:10 +0200 [thread overview]
Message-ID: <20100617114110.GB16187@attic.humilis.net> (raw)
In-Reply-To: <AANLkTikL6C9Ize1K-Hixsb9PEePezAQDR7FbQ7EemiRX@mail.gmail.com>
Yan, Zheng wrote (ao):
> what will happen if you keep deleting files using 2.6.35?
>From the list: "Things you don't want your fs developer to say" ;-)
PS, I am a very happy btrfs user on several systems (including
AMR based OpenRD-Client and SheevaPlug, and large 64bit servers), so no
flame intended ;-)
Sander
--
Humilis IT Services and Solutions
http://www.humilis.net
next prev parent reply other threads:[~2010-06-17 11:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 17:48 Still ENOSPC problems with 2.6.35-rc3 Johannes Hirte
2010-06-16 23:12 ` Yan, Zheng
2010-06-16 23:56 ` Johannes Hirte
2010-06-17 0:47 ` Yan, Zheng
2010-06-17 11:41 ` Sander [this message]
2010-06-17 13:46 ` Johannes Hirte
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=20100617114110.GB16187@attic.humilis.net \
--to=sander@humilis.net \
--cc=chris.mason@oracle.com \
--cc=johannes.hirte@fem.tu-ilmenau.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=yanzheng@21cn.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 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).