From: Mike Thomas <btrfs@thomii.com>
To: "'Fajar A. Nugraha'" <list@fajar.net>
Cc: <linux-btrfs@vger.kernel.org>
Subject: RE: btrfs errors
Date: Fri, 2 Dec 2011 07:42:49 -0500 [thread overview]
Message-ID: <000601ccb0ef$e6910dc0$b3b32940$@thomii.com> (raw)
In-Reply-To: <CAG1y0sdaMA=ei=v7tGHmUT1qT3ELftoqUHnO-jXmjfE5LvpC_A@mail.gmail.com>
I figured that would be the case but still thought maybe it could possi=
bly
be somewhat useful.
I will give the newer kernel a try... BTW is nfs export "supported" ye=
t?
Thanks, Mike
BTW Awesome work on btrfs it's fantastic, it's saved my household so ma=
ny
times when my wife has accidently deleted a ton of photos...
-----Original Message-----
=46rom: Fajar A. Nugraha [mailto:list@fajar.net]=20
Sent: Friday, December 02, 2011 7:39 AM
To: Mike Thomas
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs errors
On Fri, Dec 2, 2011 at 7:34 PM, Mike Thomas <btrfs@thomii.com> wrote:
> Hi, I've been using btrfs for a while now, I've been utilizing=20
> snapshotting nightly/weekly/monthly.=A0 During the weekly I also do a=
=20
> backup of the filesystem to an ext4 filesystem.=A0 My storage is a li=
nux md
raid 5 volume.
> I've recently noticed these errors in the logs during the backup of=20
> the files to the ext4 filesystem.=A0 I am running RHEL 6.1
> (2.6.32-131.0.15.el6.x86_64)
that's like dinosaur age, in btrfs terms :P
>
> I'd like to help in any way I can so I thought I'd post here to see i=
f=20
> there is anything I can do to help.
I'd try compiling latest 3.2-rc kernel. or Chris' for-linus tree
(http://git.kernel.org/?p=3Dlinux/kernel/git/mason/linux-btrfs.git;a=3D=
shortlog;
h=3Drefs/heads/for-linus)
which is based on 3.1, and see if it goes away.
--
=46ajar
--
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-12-02 12:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AFB7E63B2FEE4449B3DBF47BC3AA36F085956971@server2k8.thomii.com>
2011-12-02 12:34 ` btrfs errors Mike Thomas
2011-12-02 12:38 ` Fajar A. Nugraha
2011-12-02 12:42 ` Mike Thomas [this message]
2018-03-14 2:07 higuita
2018-03-14 4:24 ` Chris Murphy
2018-03-17 1:34 ` higuita
2018-03-17 17:31 ` Chris Murphy
[not found] <632175948.36.1565689408284.JavaMail.gkos@xpska>
2019-08-13 9:48 ` Konstantin V. Gavrilenko
2019-08-13 10:55 ` Qu Wenruo
[not found] ` <744798339.29.1565703591504.JavaMail.gkos@xpska>
2019-08-13 14:01 ` Qu Wenruo
[not found] ` <1425294964.32.1565720950325.JavaMail.gkos@xpska>
2019-08-13 23:24 ` Qu Wenruo
2019-08-14 9:12 ` Konstantin V. Gavrilenko
-- strict thread matches above, loose matches on Subject: below --
2021-05-09 22:08 BTRFS Errors Michael Stickel
2021-05-15 2:24 ` Zygo Blaxell
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='000601ccb0ef$e6910dc0$b3b32940$@thomii.com' \
--to=btrfs@thomii.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=list@fajar.net \
/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.