Package: mdadm
Version: 2.5.2-7
Severity: normal
Tags: patch

checkarray --all gives the following error on a system with both RAID1
and RAID0 arrays:

checkarray: E: /sys/block/md4/md/sync_action not writeable.

Patch below fixes this by making --all only select devices that have
md/sync_action.

Paul

--- checkarray  2006-07-23 01:20:44.000000000 +0100
+++ checkarray.old      2006-07-23 01:17:37.000000000 +0100
@@ -96,7 +96,7 @@
   exit 3
 fi
 
-[ $all = 1 ] && devices="$(ls -1 /sys/block/md*/md/sync_action | cut -d/ -f4)"
+[ $all = 1 ] && devices="$(ls -d1 /sys/block/md* | cut -d/ -f4)"
 
 for dev in $devices; do
   SYNC_ACTION_CTL=/sys/block/$dev/md/sync_action


--- /proc/mdstat:
Personalities : [raid1] [raid0] 
md4 : active raid0 md2[0] md3[1]
      
md3 : active raid1 hda5[0] sdc1[1]
      
md2 : active raid1 sda2[0] sdb1[1]
      
md1 : active raid1 sdb2[0] sdc2[1]
      
--- initrd.img-2.6.17-w64:

--- /proc/modules:
dm_mod 62992 6 - Live 0xffffffff88029000
raid0 8704 1 - Live 0xffffffff88025000
raid1 24640 3 - Live 0xffffffff8801d000
md_mod 83420 6 raid0,raid1, Live 0xffffffff88007000

--- volume detail:


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-w64
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)

Versions of packages mdadm depends on:
ii  debconf [debconf-2.0]         1.5.2      Debian configuration management sy
ii  libc6                         2.3.6-15   GNU C Library: Shared libraries
ii  lsb-base                      3.1-10     Linux Standard Base 3.1 init scrip
ii  makedev                       2.3.1-82   creates device files in /dev

Versions of packages mdadm recommends:
ii  postfix [mail-transport-agent 2.3.0-1    A high-performance mail transport 

-- debconf information:
* mdadm/autostart: false
  mdadm/initrdstart: all
* mdadm/warning:
* mdadm/start_daemon: true
* mdadm/mail_to: paul
* mdadm/autocheck: true


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to