On Thu, Jan 5, 2017 at 12:58 PM, Eric Sandeen <sandeen@xxxxxxxxxxx> wrote:
> On 1/5/17 12:02 PM, Xingbo Wu wrote:
>> /dev/sdf is a 3TB hard drive.
>> It has 2930266584 blocks, as reported in `badblocks -wsv /dev/sdf`:
>> Checking for bad blocks in read-write mode
>> From block 0 to 2930266583
>
> 2930266583 x 1024 == 3000592980992
>
> I'd rather see what /proc/partitions and/or blockdev says about it...
>
$ cat /proc/partitions
major minor #blocks name
8 0 244198584 sda
8 1 31457280 sda1
8 2 212740096 sda2
8 48 3907018584 sdd
8 64 3907018584 sde
8 32 1953514584 sdc
8 16 1953514584 sdb
8 80 2930266584 sdf
>> However mkfs.xfs reports a larger block count:
>> `sudo mkfs.xfs /dev/sdf`:
>> meta-data=/dev/sdf isize=512 agcount=4, agsize=183141662 blks
>> = sectsz=4096 attr=2, projid32bit=1
>> = crc=1 finobt=1, sparse=0, rmapbt=0
>> data = bsize=4096 blocks=732566646, imaxpct=5
>> = sunit=0 swidth=0 blks
>> naming =version 2 bsize=4096 ascii-ci=0 ftype=1
>> log =internal log bsize=4096 blocks=357698, version=2
>> = sectsz=4096 sunit=1 blks, lazy-count=1
>> realtime =none extsz=4096 blocks=0, rtextents=0
>
> 732566646 x 4k blocks == 3000592982016 bytes
>
> Ok, that is 1024 bytes bigger. But the weird thing is that
> mkfs.xfs actually writes the last block, and fails if that fails.
>
> So let's start with what /proc/partitions says, as well as
>
> # blkdev --getsize --getsize64 /dev/sdf
>
The machines runs a up-to-dated Archlinux with Kernel 4.8.13 (64bit)
I didn't found blkdev but instead found blockdev in package
util-linux. It looks the samething.
$ sudo blockdev --getsize --getsize64 /dev/sdf
5860533168
3000592982016
> -Eric
>
>> It later leads to IO error:
>> `dmesg`:
>> [1807875.741674] blk_update_request: I/O error, dev sdf, sector 2930266664
>> [1807875.741732] blk_update_request: I/O error, dev sdf, sector 2930266664
>> [1807875.742306] XFS (sdf): metadata I/O error: block 0xaea85228
>> ("xlog_iodone") error 5 numblks 64
>> [1807875.742369] XFS (sdf): xfs_do_force_shutdown(0x2) called from
>> line 1200 of file fs/xfs/xfs_log.c. Return address =
>> 0xffffffffa024090c
>> [1807875.742381] XFS (sdf): Log I/O Error Detected. Shutting down filesystem
>> [1807875.742416] XFS (sdf): xfs_log_force: error -5 returned.
>> [1807875.742426] XFS (sdf): Please umount the filesystem and rectify
>> the problem(s)
>> [1807881.868117] XFS (sdf): xfs_log_force: error -5 returned.
>> [1807910.701836] XFS (sdf): xfs_log_force: error -5 returned.
>> [1807910.701841] XFS (sdf): Unmounting Filesystem
>> [1807910.701854] XFS (sdf): xfs_log_force: error -5 returned.
>> [1807910.701866] XFS (sdf): xfs_log_force: error -5 returned.
>>
>>
>>
>> The hard drive information:
>> Model Family: Seagate Barracuda 7200.14 (AF)
>> Device Model: ST3000DM001-9YN166
>> Serial Number: W1F03GXY
>>
--
Regards,
Wu, Xingbo (吴兴博) <wuxb45@xxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
