From: "Helmut Hullen" <Hullen@t-online.de>
To: linux-btrfs@vger.kernel.org
Subject: scrub: Inappropriate ioctl for device
Date: 01 Nov 2011 20:36:00 +0100 [thread overview]
Message-ID: <Bx1FpyLi1uB@helmut.hullen.de> (raw)
Hallo,
I'm just playing with "btrfs scrub".
Kernel 3.1 (self made)
btrfs integration-20111030 (Hugo Mills)
I have a bundle of 3 2-TByte-disks (data raid0, metadata raid1).
Since some (few) weeks one of the disks makes errors (I've reported the
problems in this mailing list).
The bundle uses the devices /dev/sdb1, /dev/sdc1 and /dev/sdg1, "btrfs
filesystem show" shows these informations.
Mounting doesn't work immediately; most times I have to run the "mount"
command three times - strange.
When I run
btrfs scrub start -r /dev/sdb1
(or another of the three disks) then I only get the error message
ERROR: getting dev info for scrub failed: Inappropriate ioctl for
device
I don't use "udev", "ls -l /dev/sdb1" shows
brw-r----- 1 root disk 8, 17 29. Apr 1995 /dev/sdb1
Running the command via "strace" shows the last lines
set_thread_area({entry_number:-1 -> 6, base_addr:0x401b6b80,
limit:1048575, seg_32bit:1, contents:0, read_exec_only:0,
limit_in_pages:1, seg_not_present:0, useable:1}) = 0
mprotect(0x401b0000, 8192, PROT_READ) = 0
mprotect(0x4004c000, 4096, PROT_READ) = 0
mprotect(0x4001d000, 4096, PROT_READ) = 0
munmap(0x40021000, 89277) = 0
set_tid_address(0x401b6be8) = 10400
set_robust_list(0x401b6bf0, 0xc) = 0
futex(0xbffe4c00, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0xbffe4c00, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1, NULL, bffe4c10) = -1 EAGAIN (Resource temporarily unavailable)
rt_sigaction(SIGRTMIN, {0x4003b520, [], SA_SIGINFO}, NULL, 8) = 0
rt_sigaction(SIGRT_1, {0x4003b5a0, [], SA_RESTART|SA_SIGINFO}, NULL, 8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0
getrlimit(RLIMIT_STACK, {rlim_cur=RLIM_INFINITY, rlim_max=RLIM_INFINITY}) = 0
uname({sys="Linux", node="Arktur.wm8.hullen.de", ...}) = 0
brk(0) = 0x806d000
brk(0x808e000) = 0x808e000
mkdir("/var", 0777) = -1 EEXIST (File exists)
mkdir("/var/lib", 0777) = -1 EEXIST (File exists)
mkdir("/var/lib/btrfs", 0777) = -1 EEXIST (File exists)
stat64("/dev/sdb1", {st_mode=S_IFBLK|0640, st_rdev=makedev(8, 17), ...}) = 0
open("/dev/sdb1", O_RDWR|O_LARGEFILE) = 3
ioctl(3, 0x8400941f, 0xbffe4554) = -1 ENOTTY (Inappropriate ioctl for device)
write(2, "ERROR: getting dev info for scru"..., 73ERROR: getting dev info for scrub failed: Inappropriate ioctl for device
) = 73
close(3) = 0
exit_group(1) = ?
--------------------------------------------------
Changing the rights of "/dev/sdb1" to 660 doesn't help - same nasty
behaviour.
What goes wrong?
Viele Gruesse!
Helmut
next reply other threads:[~2011-11-01 19:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 19:36 Helmut Hullen [this message]
2011-11-01 20:08 ` scrub: Inappropriate ioctl for device Ilya Dryomov
2011-11-01 21:10 ` Helmut Hullen
2011-11-02 12:55 ` David Sterba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Bx1FpyLi1uB@helmut.hullen.de \
--to=hullen@t-online.de \
--cc=helmut@hullen.de \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.