Bug #4735
closedidentify ioctl not supported on Centos
0%
Description
Not sure yet if this causes a problem, but I wanted to document it anyway.
Centos 6.3 and XFS filesystem
[root@gary-centos-01 ceph-0]# ceph-osd -d -i 0
2013-04-16 22:49:45.505754 7f6c55be8760 0 ceph version 0.60-469-gc2eb207 (c2eb20782b1ca237a9a6065ccbb12392dc0fa949), process ceph-osd, pid 31197
starting osd.0 at :/0 osd_data /var/lib/ceph/osd/ceph-0 /var/lib/ceph/osd/ceph-0/journal
2013-04-16 22:49:45.523970 7f6c55be8760 0 filestore(/var/lib/ceph/osd/ceph-0) mount FIEMAP ioctl is supported and appears to work
2013-04-16 22:49:45.524031 7f6c55be8760 0 filestore(/var/lib/ceph/osd/ceph-0) mount FIEMAP ioctl is disabled via 'filestore fiemap' config option
2013-04-16 22:49:45.524239 7f6c55be8760 0 filestore(/var/lib/ceph/osd/ceph-0) mount did NOT detect btrfs
2013-04-16 22:49:45.530219 7f6c55be8760 0 filestore(/var/lib/ceph/osd/ceph-0) mount syscall(SYS_syncfs, fd) fully supported
2013-04-16 22:49:45.530308 7f6c55be8760 0 filestore(/var/lib/ceph/osd/ceph-0) mount found snaps <>
2013-04-16 22:49:45.537578 7f6c55be8760 0 filestore(/var/lib/ceph/osd/ceph-0) mount: enabling WRITEAHEAD journal mode: btrfs not detected
HDIO_DRIVE_CMD(identify) failed: Inappropriate ioctl for device
2013-04-16 22:49:45.541370 7f6c55be8760 1 journal _open /var/lib/ceph/osd/ceph-0/journal fd 17: 1074769920 bytes, block size 4096 bytes, directio = 1, aio = 1
HDIO_DRIVE_CMD(identify) failed: Inappropriate ioctl for device
2013-04-16 22:49:45.604617 7f6c55be8760 1 journal _open /var/lib/ceph/osd/ceph-0/journal fd 17: 1074769920 bytes, block size 4096 bytes, directio = 1, aio = 1
2013-04-16 22:49:45.620897 7f6c55be8760 1 journal close /var/lib/ceph/osd/ceph-0/journal
^C[root@gary-centos-01 ceph-0]#
Updated by Anonymous about 11 years ago
hdparm is used to determine if write-caching is enabled for the journal device. it appears to faile for virtual devices. I think the code in this case assumes off, or at least doesn't issue a warning message about write-caching being enabled.
Updated by Sage Weil about 11 years ago
- Status changed from New to Won't Fix
the warning is harmless. it just means we can't warn the user about the writeback cache on the drive.