From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: xfs@oss.sgi.com, linux-fsdevel@vger.kernel.org
Subject: Re: clone ioctl return values
Date: Tue, 17 Nov 2015 07:12:26 -0800 [thread overview]
Message-ID: <20151117151226.GA12860@infradead.org> (raw)
In-Reply-To: <20151117002822.GA32467@birch.djwong.org>
On Mon, Nov 16, 2015 at 04:28:22PM -0800, Darrick J. Wong wrote:
> > -XFS_IOC_CLONE_RANGE: Invalid argument
> > +reflink: Invalid argument
> > Try reflink past EOF
> > -XFS_IOC_CLONE_RANGE: Invalid argument
> > +reflink: Invalid argument
> > Try to reflink a dir
> > -XFS_IOC_CLONE_RANGE: Is a directory
> > +reflink: Is a directory
>
> > Try to reflink a device
> > -XFS_IOC_CLONE_RANGE: Invalid argument
> > +/mnt/test/test-157/dev1: No such device or address
>
> Huh. How did you get -ENODEV here? I ran this on 4.3 and got -EINVAL.
Turns out this is because my system doesn't have the ramdisk driver
built into the kernel, so opening your block device with major 8, minor
0 already fails. Might be better to create a char device with
major 1, minor 3 (dev null) as that should always be present.
prev parent reply other threads:[~2015-11-17 15:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 12:04 clone ioctl return values Christoph Hellwig
2015-11-17 0:28 ` Darrick J. Wong
2015-11-17 10:54 ` Christoph Hellwig
2015-11-17 13:57 ` Chris Mason
2015-11-17 15:22 ` Christoph Hellwig
2015-11-17 15:33 ` Al Viro
2015-11-17 15:36 ` Christoph Hellwig
2015-11-17 18:42 ` Chris Mason
2015-11-18 3:01 ` Darrick J. Wong
2015-11-18 15:11 ` Christoph Hellwig
2015-11-17 15:12 ` Christoph Hellwig [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=20151117151226.GA12860@infradead.org \
--to=hch@infradead.org \
--cc=darrick.wong@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=xfs@oss.sgi.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).