Philipp Kern wrote, Sunday, January 04, 2009 12:14 AM
I just got alerted by mdadm with this: /usr/share/mdadm/checkarray: line 167: echo: write error: Device or resource busy
We've had the same issue for the past couple of monthly checks. I hadn't reported it as everything seemed to be working and no-one else seemed to be experiencing it.
Actually it tried to write to /sys/block/md0/md/sync_action and it seems that md0 does not like that. It works fine with md1 and md2. The mdstat is as follows:
[...]
The md devices were created by a setup script and md0 holds the swap space which is, I think, the rationale for using auto-read-only.
Our setup's similar. The arrays were created by lenny d-i (RC1) and the swap array (md1) is marked as auto-read-only.
Aside from the slightly worrying error message (at least at first glance), the arrays after the swap never actually get checked, as the failure causes the script to exit.
Adam
-- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
