public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Scott <nathans@debian.org>
To: Phil White <cerise-xfs@littlegreenmen.armory.com>
Cc: xfs@oss.sgi.com
Subject: Re: Problem with mkfs.xfs on a regular file
Date: Tue, 26 Nov 2013 21:38:20 -0500 (EST)	[thread overview]
Message-ID: <1428728255.17190956.1385519900454.JavaMail.root@redhat.com> (raw)
In-Reply-To: <20131127023119.GB13101@boogeyman>



----- Original Message -----
> ...
> It's trying to read/write 512 bytes at the beginning of the file which seems
> reasonably innocuous.  I double checked the man page which says that under
> 2.6, O_DIRECT writes can be aligned to 512 bytes without a problem.  sbp
> comes
> out with 4096 in blocksize and 512 in sectsize when zero_old_xfs_structures()
> is called and the first error comes up, so I'm at a loss for what's going
> wrong.

The filesystem backing the new /root/image file doesn't support direct I/O?

cheers.

--
Nathan

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2013-11-27  2:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-27  2:31 Problem with mkfs.xfs on a regular file Phil White
2013-11-27  2:36 ` Phil White
2013-11-27  2:38 ` Nathan Scott [this message]
2013-11-27  2:41   ` Phil White
2013-11-27  2:47     ` Dave Chinner
2013-11-27  2:47 ` Dave Chinner
2013-11-28  2:39   ` Eric Sandeen
2013-11-28  5:16     ` Dave Chinner
2013-11-28  5:34       ` Eric Sandeen
2013-11-28 10:01         ` Dave Chinner
2013-11-28 11:47           ` Phil White
2013-11-28 15:38             ` Eric Sandeen
2013-11-28 15:32           ` Eric Sandeen
2013-11-28 21:12             ` Dave Chinner
2013-11-29  1:28               ` 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=1428728255.17190956.1385519900454.JavaMail.root@redhat.com \
    --to=nathans@debian.org \
    --cc=cerise-xfs@littlegreenmen.armory.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