From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: pcacjr@zytor.com, xfs@oss.sgi.com
Subject: Re: syslinux xfs support
Date: Wed, 16 Oct 2013 07:54:34 +1100 [thread overview]
Message-ID: <20131015205434.GT4446@dastard> (raw)
In-Reply-To: <20131015203319.GA20191@infradead.org>
On Tue, Oct 15, 2013 at 01:33:19PM -0700, Christoph Hellwig wrote:
> Hi Paulo,
>
> just wondering what the state of the xfs support for syslinux is? I
> talked to Peter at Linuxcon and he thought it's merged, but looking at
> the kernel.org tree I can't find the support.
>
> Also when looking over your branches I noticed that you're using a free
> sector in the first filesystem block to store the bootloader. If we
> want to go down that route we need to make sure to reserve this sector,
> otherwise it might get taken up by newly added metadata.
It's also worth pointing out that there's no guarantee that there's
a free sector in the first filesystem block. It's only by luck that
there's free sectors on the default config (512 byte sector, 4
sector sized AG headers, 4k filesystem block). If we have <= 2k filesystem
block there are no free "pad" sectors that can be used, 4k sectors
mean no free sectors either, etc.
Much better would be to create a sector sized file and use fiemap to
get the disk address of the block and feed that into the
bootloader. That works for all filesystems without needing to know
anything about the underlying filesystem structures......
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-10-15 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 20:33 syslinux xfs support Christoph Hellwig
2013-10-15 20:54 ` Dave Chinner [this message]
2013-10-16 5:48 ` Chris Murphy
2013-10-16 10:50 ` Dave Chinner
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=20131015205434.GT4446@dastard \
--to=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=pcacjr@zytor.com \
--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