Actions
Bug #10798
closedmkfs.ext4 fails with "apparently in use by the system"
% Done:
0%
Source:
other
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Crash signature (v1):
Crash signature (v2):
Description
http://pulpito.ceph.com/loic-2015-02-09_11:30:40-rgw-dumpling-backports---basic-multi/748360/
2015-02-09T02:42:33.041 INFO:tasks.ceph:['mkfs.ext4'] on /dev/sdg on ubuntu@mira059.front.sepia.ceph.com 2015-02-09T02:42:33.042 INFO:teuthology.orchestra.run.mira059:Running: 'yes | sudo mkfs.ext4 /dev/sdg' 2015-02-09T02:42:33.125 INFO:teuthology.orchestra.run.mira059.stderr:mke2fs 1.42.9 (4-Feb-2014) 2015-02-09T02:42:33.126 INFO:teuthology.orchestra.run.mira059.stdout:/dev/sdg is entire device, not just one partition! 2015-02-09T02:42:33.126 INFO:teuthology.orchestra.run.mira059.stderr:/dev/sdg is apparently in use by the system; will not make a filesystem here! 2015-02-09T02:42:33.127 INFO:teuthology.orchestra.run.mira059.stdout:Proceed anyway? (y,n) 2015-02-09T02:42:33.127 INFO:tasks.ceph:['mkfs.ext4', '-f'] on /dev/sdg on ubuntu@mira059.front.sepia.ceph.com
the error is shadowed by http://tracker.ceph.com/issues/10797 ceph.py fallback fails because mkfs.ext4 does not have \-f option on trusty
Updated by Dan Mick over 8 years ago
- Status changed from New to Need More Info
- Regression set to No
Maybe this was about losing the -f flag? Is it still an issue?
Updated by Loïc Dachary over 8 years ago
One would have to read the code to see if the problem is still there. I'm not familiar enough with teuthology to answer immediately.
Updated by Dan Mick over 8 years ago
This also migth have to do with the disk having dmraid trash on it (some of our "new" replacement drives seem to have been used in a software raid and retain the label). If anyone sees this, try seeing what dmraid -r shows.
Updated by Dan Mick over 8 years ago
it doesn't appear to be the case with mira059 at the moment.
Updated by Sage Weil about 8 years ago
- Status changed from Need More Info to Resolved
assuming this is fixed on that mira
Actions