From: Miguel Garrido <miguel@mjgar.com>
To: CACook@quantum-sci.com
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Cannot Deinstall a Debian Package
Date: Thu, 5 May 2011 19:06:19 -0400 [thread overview]
Message-ID: <BANLkTikve7YaHWjqOmHUvVd3psqYs022EA@mail.gmail.com> (raw)
In-Reply-To: <201105051533.07880.CACook@quantum-sci.com>
On Thu, May 5, 2011 at 6:33 PM, <CACook@quantum-sci.com> wrote:
>
> On Thursday 5 May, 2011 14:48:49 cwillu wrote:
> > How old was the filesystem? =A0It might just have been lingering
> > problems from an older kernel, which would be cleared up entirely b=
y
> > the balance you just ran.
>
> I specifically set up the filesystem with the Live CD of the M- relea=
se of Ubuntu, so as to be using a much newer kernel than Debian's. =A0T=
his was in December. =A0Then I used the Debian net install CD in Expert=
mode to install the OS.
>
> I took all pains to be using the newest OS available to set up the di=
sks, so as to take advantage of WD's Advanced Format, and the newest im=
provements to BTRFS. =A0But the balance is still going after more than =
an hour.
>
> I am seeing drastically conflicting info from df and btrfs filesystem=
df, which is inexplicable.
>
https://btrfs.wiki.kernel.org/index.php/FAQ#Why_does_df_show_incorrect_=
free_space_for_my_RAID_volume.3F
The above link may help explain why df and btrfs fi df differ.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-05-05 23:06 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 19:27 Cannot Deinstall a Debian Package CACook
2011-05-03 21:26 ` Fajar A. Nugraha
2011-05-03 22:20 ` CACook
2011-05-03 23:02 ` Chuck Burns
2011-05-04 0:12 ` CACook
2011-05-04 0:25 ` Chuck Burns
2011-05-04 1:20 ` Chris Samuel
2011-05-04 2:44 ` Fajar A. Nugraha
2011-05-04 9:51 ` Sander
2011-05-05 14:49 ` CACook
2011-05-05 18:09 ` CACook
2011-05-05 19:09 ` cwillu
2011-05-05 19:28 ` cwillu
2011-05-05 19:50 ` CACook
2011-05-05 19:55 ` Chris Mason
2011-05-05 20:32 ` CACook
2011-05-05 20:40 ` cwillu
2011-05-05 21:40 ` CACook
2011-05-05 21:48 ` cwillu
2011-05-05 22:33 ` CACook
2011-05-05 23:06 ` Miguel Garrido [this message]
2011-05-06 3:53 ` Helmut Hullen
2011-05-06 6:49 ` Sander
2011-05-05 20:31 ` cwillu
2011-05-05 20:57 ` CACook
2011-05-05 20:59 ` Lars Wirzenius
2011-05-05 21:48 ` CACook
2011-05-05 21:50 ` cwillu
2011-05-05 21:11 ` cwillu
2011-05-06 6:43 ` Sander
2011-05-06 6:33 ` Sander
2011-05-06 12:09 ` CACook
2011-05-06 12:20 ` Sander
2011-05-06 12:57 ` CACook
2011-05-06 13:21 ` Sander
2011-05-06 13:56 ` CACook
2011-05-06 14:17 ` Sander
2011-05-06 14:53 ` CACook
2011-05-06 14:58 ` Sander
2011-05-06 15:15 ` CACook
2011-05-06 17:09 ` CACook
2011-05-06 20:04 ` CACook
2011-05-06 20:16 ` Tomasz Torcz
2011-05-06 20:56 ` CACook
2011-05-06 21:23 ` Peter Stuge
2011-05-06 20:40 ` Sander
2011-05-06 20:51 ` Peter Stuge
2011-05-06 21:20 ` CACook
2011-05-06 21:28 ` Peter Stuge
2011-05-06 21:32 ` Hugo Mills
2011-05-06 22:17 ` David G Beausang
2011-05-07 1:51 ` C Anthony Risinger
2011-05-07 2:05 ` C Anthony Risinger
[not found] ` <201105062008.26159.CACook@quantum-sci.com>
2011-05-07 6:21 ` C Anthony Risinger
2011-05-07 7:03 ` Helmut Hullen
2011-05-06 13:30 ` Helmut Hullen
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=BANLkTikve7YaHWjqOmHUvVd3psqYs022EA@mail.gmail.com \
--to=miguel@mjgar.com \
--cc=CACook@quantum-sci.com \
--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).