Pwrite64 Failed Input/output Error
Contents |
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack xfs metadata i/o error Overflow the company Business Learn more about hiring developers or posting ads with us i/o error detected. shutting down filesystem Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and xfs superblock read failed network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top mkfs.xfs: libxfs_device_zero xfs can't read superblock write failed: Input/output error up vote 0 down vote favorite I can't find a way to create a filesystem on one of my disks. first i'm geting the following output: [root@~]# mkfs.xfs /dev/sdb1 mkfs.xfs: /dev/sdb1 appears to contain a partition table (dos). mkfs.xfs: Use the -f option to force overwrite. after using -F flag: [root@~]# mkfs.xfs -f /dev/sdb1 meta-data=/dev/sdb1 isize=256 agcount=32, agsize=22892696 blks = sectsz=512 attr=2 data = bsize=4096 blocks=732566272, imaxpct=5 =
Existing Superblock Read Failed: Input/output Error
sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0 log =internal log bsize=4096 blocks=357698, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 **mkfs.xfs: libxfs_device_zero write failed: Input/output error** /dev/sdb: Disk /dev/sdb: 3001GB 1 1049kB 3001GB 3001GB primary Linux: Centos 6.3 Linux 1 2.6.32-279.el6.x86_64 #1 SMP Fri Jun 22 12:19:21 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux what i've tried so far: recreating partition with parted rm 1 linux filesystems xfs share|improve this question edited Oct 24 '12 at 21:29 ewwhite 152k47302579 asked Oct 24 '12 at 20:17 Crazy_Bash 13739 Disk /dev/sdb: 3001GB 1 1049kB 3001GB 3001GB primary –Crazy_Bash Oct 24 '12 at 20:26 Version of Linux and distribution? –ewwhite Oct 24 '12 at 20:33 Centos 6.3 Linux 1 2.6.32-279.el6.x86_64 #1 SMP Fri Jun 22 12:19:21 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux –Crazy_Bash Oct 24 '12 at 20:36 add a comment| 1 Answer 1 active oldest votes up vote 1 down vote mkfs.xfs: libxfs_device_zero write failed: Input/output error The message is very clear: it's a hardware problem. If it's a simple SATA or SAS drive, check connections, look dmesg for driver error messages. You could also give badblocks a try; my guess is that the disk is failing and needs to be replaced, plain and simple. share|imp
Threaded Open this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ xfs_check/xfs_repair reports corruption immediately after creating filesystem This post has NOT been accepted by the mailing
Repair Xfs Superblock
list yet. I am trying to debug several anomalous behaviors with xfs. xfs error 5 returned Here's some background. I have a custom block device driver that my company has been using in their product xfs_repair bad magic number for about a year an a half. Until now, we have been using it with ext4 with some of the latest features like discard and lazy_itable_init. We have hundreds of http://serverfault.com/questions/441980/mkfs-xfs-libxfs-device-zero-write-failed-input-output-error customers and have run hours and hours of tests and have never seen any corruption that wasn't purposely induced. We currently support RHEL 6.x with the 2.6.32 kernel (with RHEL backports), but we would like to switch to xfs because it supports much larger filesystems than ext4 on RHEL6 and it's more scalable. We also test heavily with a more recent http://xfs.9218.n7.nabble.com/xfs-check-xfs-repair-reports-corruption-immediately-after-creating-filesystem-td35011.html Ubuntu 12.04 running a 3.2x kernel (3.2.0-59-generic to be more exact, more on this later), but this is not in production. We can change the block device size at load time so for quick testing, we create a 1GiB drive. Here's what the geometry looks like, which is pretty typical for a 1GiB drive, which is very small by today's standards even for a USB stick, but I digress. $ sudo hdparm -g /dev/cbd0 /dev/cbd0: geometry = 1024/64/32, sectors = 2097152, start = 0 I have a tool that also prints some results back of various ioctls, the output should be self explanatory. $ sudo ./specs /dev/cbd0 Device: /dev/cbd0 BLKBSZGET: 512 BLKSSZGET: 512 BLKGETSIZE64: 1073741824 HDIO_GETGEO: cylinders: 1024 heads: 64 sectors: 32 start: 0 Geometry check: geometry size matches BLKGETSIZE64 exactly What's odd is that if I create an xfs filesystem on Ubuntu 12.04, it attempts to write off the edge of the disk. The last I/O request overlaps the end of the disk. That is, it's start sector is near the end of the disk (in bounds), but it's transfer len
on 2.6.27.3 (was: mkfs.xfs segfaults) Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] Sven, what's your exact block device stack? Is LVM and/or MD http://lists.linbit.com/pipermail/drbd-user/2008-October/010663.html in play anywhere? Cheers, Florian Sven Geggus wrote: > Florian Haas
Tue, 29 Jan 2002 12:07:32 +1100 Sender: owner-linux-xfs@xxxxxxxxxxx hi, On Mon, Jan 28, 2002 at 12:02:59PM -0500, Dave Sill wrote: > I've got a terabyte RAID that I'm trying to set up as a single XFS > filesystem. mkfs fails with: > > [root@malachite root]# mkfs.xfs -f /dev/sdb1 > meta-data=/dev/sdb1 isize=256 agcount=224, agsize=1048576 blks > data = bsize=4096 blocks=234870292, imaxpct=25 > = sunit=0 swidth=0 blks, unwritten=0 > = imaxbits=32 > naming =version 2 bsize=4096 > log =internal log bsize=4096 blocks=28670 > realtime =none extsz=65536 blocks=0, rtextents=0 > mkfs.xfs: read failed: Input/output error > mkfs.xfs: data size check failed > mkfs.xfs: mount initialization failed > [root@malachite root]# Basically, what happens here is mkfs.xfs asks the device how big it is (using the BLKGETSIZE ioctl) and before starting to write to the disk, mkfs seeks to 4K from the end of the device and issues a read (to validate the size which the device driver gave it). It looks like for your terabyte RAID, this read is failing (the driver is giving EIO), hence the message "data size check failed". mkfs.xfs will refuse to run on a device which exhibits this anti- social behavior. > I had no problems mkfs'ing it as e2fs, e3fs, and reiserfs. These programs are not doing this lseek/read check to validate the size of the device. > I'm running under the 1.02a installer on an Athlon: > > [root@malachite root]# uname -a > Linux malachite 2.4.9-13SGI_XFS_1.0.2 #1 Thu Nov 15 14:28:44 CST 2001 i686 > unknown > [root@malachite root]# > > I installed the xfs programs from the RPM: > > xfsprogs-1.3.13-0.i386.rpm > > Any ideas? > Your terabyte RAID device driver seems to have a bug in either the code which reports its size, or in reading near the end of the device. Hope this helps. cheers. -- Nathan [Morewiththissubject...]