While in IBM class we found we could create and use XFS under SLES 9
SP4, so it appears that while we are SLES 9 SP3 (where xfs is
supported), there is something we are missing. 

Thanks, 
Bob  

-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of
Stricklin, Raymond J
Sent: Friday, March 14, 2008 4:05 PM
To: [email protected]
Subject: Re: Using xfs file sys

With SLES10 SP1, 'mkfs -t xfs' fails without '-s size=4096'.

This is the resulting output from 'mkfs':

---(begin)
mkfs.xfs: warning - cannot set blocksize on block device /dev/dasdd1:
Invalid argument
Warning: the data subvolume sector size 512 is less than the sector size
reported by the device (4096).
meta-data=/dev/dasdd1            isize=256    agcount=8, agsize=75102
blks
         =                       sectsz=512   attr=0
data     =                       bsize=4096   blocks=600816, imaxpct=25
         =                       sunit=0      swidth=0 blks, unwritten=1
naming   =version 2              bsize=4096
log      =internal log           bsize=4096   blocks=2560, version=1
         =                       sectsz=512   sunit=0 blks
realtime =none                   extsz=4096   blocks=0, rtextents=0
mkfs.xfs: pwrite64 failed: Invalid argument
mkfs.xfs: read failed: Invalid argument
---(end)

A valid xfs filesystem is not written to disk, despite the output
describing the resulting filesystem characteristics. 

Specifying '-s size=4096' results in a valid filesystem, and this
output:

---(begin)
meta-data=/dev/dasdd1            isize=256    agcount=8, agsize=75102
blks
         =                       sectsz=4096  attr=0
data     =                       bsize=4096   blocks=600816, imaxpct=25
         =                       sunit=0      swidth=0 blks, unwritten=1
naming   =version 2              bsize=4096
log      =internal log           bsize=4096   blocks=2560, version=2
         =                       sectsz=4096  sunit=1 blks
realtime =none                   extsz=4096   blocks=0, rtextents=0
---(end) 

If I attempt to create the filesystem on the non-partitioned disk device
(/dev/dasdd) rather than the partitioned disk device (/dev/dasdd1), I
get the same output as above (no errors), but the device is unmountable.

I would second Mark Post's suggestion that a whole-disk partition be
created with 'fdasd -a' and the filesystem be created on that device
instead (/dev/dasdj1).

ok
r.


> -----Original Message-----
> From: Fargusson.Alan [mailto:[EMAIL PROTECTED]
> Sent: Friday, March 14, 2008 10:54 AM
> To: [email protected]
> Subject: Re: Using xfs file sys
> 
> I don't think the DASD driver supports setting the sector size.  Try 
> without the "-s size=4096".  The device is probably formatted in 4096 
> byte blocks anyway.
> 
> -----Original Message-----
> From: Linux on 390 Port [mailto:[EMAIL PROTECTED]
> Behalf Of Dott, Robert
> Sent: Friday, March 14, 2008 10:38 AM
> To: [email protected]
> Subject: Using xfs file sys
> 
> 
> We are trying to evaluate XFS performance, but cannot get the mkfs to 
> make a xfs filesys. We are sles9 sp3 and when we try to do the mkfs 
> command get the following:
>  
> mkfs -t xfs -s size=4096 /dev/dasdj
> mkfs.xfs: warning - cannot set blocksize on block device /dev/dasdj:
> Invalid argument
> meta-data=/dev/dasdj isize=256 agcount=8, agsize=70605 blks =
> sectsz=4096 data = bsize=4096 blocks=564840, imaxpct=25 = sunit=0 
> swidth=0 blks, unwritten=1 naming =version 2
> bsize=4096 log =internal log bsize=4096 blocks=2560,
> version=2 = sectsz=4096 sunit=1 blks realtime =none
> extsz=65536 blocks=0, rtextents=0
>  
> any suggestions appreciated. 
>  
> thanks,
> bob
>  
> Bob Dott
> AIT Technical Support
> Application Hosting
> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
> (502)-560-2908
>  
> 
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions, send 
> email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or 
> visit http://www.marist.edu/htbin/wlvindex?LINUX-390
> 
> ______________________________________________________________
> ____________________________________
> 
> CONFIDENTIALITY NOTICE: This email from the State of California is for

> the sole use of the intended recipient and may contain confidential 
> and privileged information.  Any unauthorized review or use, including

> disclosure or distribution, is prohibited.  If you are not the 
> intended recipient, please contact the sender and destroy all copies 
> of this email.
> 
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions, send 
> email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or 
> visit http://www.marist.edu/htbin/wlvindex?LINUX-390
> 

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to