Linux NILFS development
 help / color / mirror / Atom feed
From: dexen deVries <dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: FIBMAP ioctl missing
Date: Thu, 24 Feb 2011 23:34:37 +0100	[thread overview]
Message-ID: <201102242334.38044.dexen.devries@gmail.com> (raw)

Hello,

as NILFS2 doesn't implement the FIBMAP ioctl, LILO cannot be used on it.
I've just learned about it the hard way -- after migrating computer's only 
filesystem to NILFS2, running LILO returns:
ioctl FIBMAP: Invalid argument

I see the FS_IOC_FIEMAP is implemented; perhaps some wrapper around could be 
used to provide FIBMAP as well?


Regards,
-- 
dexen deVries

[[[↓][→]]]

> how does a C compiler get to be that big? what is all that code doing?

iterators, string objects, and a full set of C macros that ensure
boundary conditions and improve interfaces.

ron minnich, in response to Charles Forsyth

http://9fans.net/archive/2011/02/90
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2011-02-24 22:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-24 22:34 dexen deVries [this message]
     [not found] ` <201102242334.38044.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-02-25  0:21   ` FIBMAP ioctl missing Jérôme Poulin
2011-02-25  8:02     ` dexen deVries
     [not found]       ` <201102250902.46443.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-02-25 11:34         ` Ryusuke Konishi
     [not found]           ` <20110225.203423.220041947.ryusuke-sG5X7nlA6pw@public.gmane.org>
2011-02-25 11:45             ` dexen deVries
     [not found]           ` <201102251244.06554.dexen.devries@gmail.com>
     [not found]             ` <201102251244.06554.dexen.devries-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-02-25 14:30               ` Ryusuke Konishi

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=201102242334.38044.dexen.devries@gmail.com \
    --to=dexen.devries-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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