2.6.26 (x86 vs. x86_64) different /sys directory structure for md?
From: Justin Piszcz <hidden>
Date: 2008-08-31 10:56:30
Also in:
lkml
Have two hosts, an (md) raid5 on each: Linux p26 2.6.26 #2 SMP Sat Jul 26 13:23:40 EDT 2008 i686 GNU/Linux Linux p63 2.6.26 #2 SMP Sat Jul 26 08:21:07 EDT 2008 x86_64 GNU/Linux Was going to run a check on my raids: echo check > sync_action I noticed: For x86 (Debian Testing), the path to sync_action is: /sys/block/md0/md/sync_action For x86_64 (Debian Testing), the path to sync_action is: /sys/devices/virtual/block/md0/md/sync_action p26:/dev# find /sys/|grep -i sync_action /sys/block/md0/md/sync_action p26:/dev# p63:~# find /sys/|grep -i sync_action /sys/devices/virtual/block/md0/md/sync_action /sys/devices/virtual/block/md3/md/sync_action /sys/devices/virtual/block/md2/md/sync_action /sys/devices/virtual/block/md1/md/sync_action p63:~# The kernels are compiled similarly in terms of overall configuration, I will need to take this into account for scripting array checks etc, but I was curious why are they different between architectures and is it going to change in the future? Should one take the path to sync_action with a grain of salt? Or do I have an incorrect configuration option specified somewhere that had made this occur? http://home.comcast.net/~jpiszcz/20080831/p26-config.txt http://home.comcast.net/~jpiszcz/20080831/p63-config.txt Justin.