From: Marc MERLIN <marc@merlins.org>
To: linux-btrfs@vger.kernel.org
Subject: btrfs userland interface isn't 32/64bit clean (breaks lsattr and btrfs send)
Date: Sun, 23 Feb 2014 21:51:03 -0800 [thread overview]
Message-ID: <20140224055103.GA15937@merlins.org> (raw)
I was trying to make sense out of this:
gargamel:~# lsattr
lsattr: Inappropriate ioctl for device While reading flags on ./satapmtool
lsattr: Inappropriate ioctl for device While reading flags on ./usbreset
As well as the btrfs send issue I reported:
gargamel:/mnt/btrfs_pool1# btrfs send media_ro.20140222_11:12:53 | less
At subvol media_ro.20140222_11:12:53
ERROR: send ioctl failed with -25: Inappropriate ioctl for device
I was trying to figure out why it was failing on one system while it was working
on my other ones with the same kernel.
In the end I pinned it down to this:
3.13.5's kernel/userland interface fails if my kernel is 64bit and my
userland 32bit.
lsattr and btrfs send, and maybe more things fail, but they started working
the moment I updated my kernel to 32bit
Is this difficult to fix?
Do I need to file bugs with some folks, or this mail is enough?
Thanks,
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/
next reply other threads:[~2014-02-24 5:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 5:51 Marc MERLIN [this message]
2014-02-24 6:32 ` btrfs userland interface isn't 32/64bit clean (breaks lsattr and btrfs send) Duncan
2014-02-24 8:29 ` Hugo Mills
2014-02-24 8:43 ` Duncan
2014-02-25 6:51 ` Marc MERLIN
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=20140224055103.GA15937@merlins.org \
--to=marc@merlins.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 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.