From: Marc MERLIN <marc@merlins.org>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs userland interface isn't 32/64bit clean (breaks lsattr and btrfs send)
Date: Mon, 24 Feb 2014 22:51:34 -0800 [thread overview]
Message-ID: <20140225065134.GE3521@merlins.org> (raw)
In-Reply-To: <pan$3f644$bd8e6a71$2603a9b4$2382ccea@cox.net>
On Mon, Feb 24, 2014 at 08:43:44AM +0000, Duncan wrote:
> Hugo Mills posted on Mon, 24 Feb 2014 08:29:38 +0000 as excerpted:
>
> > On Mon, Feb 24, 2014 at 06:32:14AM +0000, Duncan wrote:
> >>
> >> This is a known issue. There's patches in the pipeline for 32-bit
> >> userspace on a 64-bit kernel, already.
> >
> > If you mean my recent patch, that's only for receive. I've not
> > noticed any other issues on my 32/64 system, but I've not done much with
> > it either (with btrfs, it's only really used for btrfs receive --
> > everything else is ext4).
>
> Thanks. Yes, I believe that's what I had in mind. So apparently there's
> more needed. (I /think/ I might have seen at least one additional patch
> float by for 32/64, but as it's out of my usage domain I'm not paying
> /that/ much attention to it, so perhaps not.)
In the meantime, if that helps someone, on debian it's trivial to get
64bit for some packages. All I had to do was this:
gargamel:/usr/src# dpkg --add-architecture amd64
gargamel:/usr/src# dpkg --print-foreign-architectures
amd64
gargamel:/usr/src# apt-get install e2fsprogs:amd64 btrfs-tools:amd64
And that's it.
Now I'm back in business with a 64bit kernel.
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | PGP 1024R/763BE901
prev parent reply other threads:[~2014-02-25 6:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 5:51 btrfs userland interface isn't 32/64bit clean (breaks lsattr and btrfs send) Marc MERLIN
2014-02-24 6:32 ` Duncan
2014-02-24 8:29 ` Hugo Mills
2014-02-24 8:43 ` Duncan
2014-02-25 6:51 ` Marc MERLIN [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=20140225065134.GE3521@merlins.org \
--to=marc@merlins.org \
--cc=1i5t5.duncan@cox.net \
--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).