xfs
[Top] [All Lists]

Re: Problem with mkfs.xfs on a regular file

To: Nathan Scott <nathans@xxxxxxxxxx>
Subject: Re: Problem with mkfs.xfs on a regular file
From: Phil White <cerise-xfs@xxxxxxxxxxxx>
Date: Tue, 26 Nov 2013 18:41:19 -0800
Cc: Phil White <cerise-xfs@xxxxxxxxxxxxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <1428728255.17190956.1385519900454.JavaMail.root@xxxxxxxxxx>
References: <20131127023119.GB13101@boogeyman> <1428728255.17190956.1385519900454.JavaMail.root@xxxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
On Tue, Nov 26, 2013 at 09:38:20PM -0500, Nathan Scott wrote:
> ----- 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.

The filesystem backing /root/image is xfs.  Good guess though.

For the record:
caliban mnt # xfs_info /
meta-data=/dev/root              isize=256    agcount=4, agsize=25685952 blks
         =                       sectsz=4096  attr=2
data     =                       bsize=4096   blocks=102743808, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0
log      =internal               bsize=4096   blocks=50167, version=2
         =                       sectsz=4096  sunit=1 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0

-Phil

<Prev in Thread] Current Thread [Next in Thread>