* Re: [PATCH V2 2/2] Add casts for the addr arg of connect and bind
From: NeilBrown @ 2016-01-14 21:37 UTC (permalink / raw)
To: Khem Raj, linux-raid
In-Reply-To: <1452753159-1527-2-git-send-email-raj.khem@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 367 bytes --]
On Thu, Jan 14 2016, Khem Raj wrote:
> glibc allows the addr arg to connect and socket to be any of a number
> of 'sockaddr_*' types, but musl requires 'const struct sockaddr *'
> which is in line with open group specs. So add casts to allow
> compilation with musl.
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
Thanks a lot! Both patches applied.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
^ permalink raw reply
* Add. Sense: Data synchronization mark error
From: Tejas Rao @ 2016-01-15 0:02 UTC (permalink / raw)
To: linux-raid
We are using linux raid on top of multipath devices (each jbod disk has
two paths).
Usually medium erros are handled as below. See this bug for a similar
problem but fixed in RHEL6.
https://bugzilla.redhat.com/show_bug.cgi?id=516170
Jan 12 02:15:59 kernel: sd 8:0:21:0: [sdcf] Unhandled sense code
Jan 12 02:15:59 kernel: sd 8:0:21:0: [sdcf] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
Jan 12 02:15:59 kernel: sd 8:0:21:0: [sdcf] Sense Key : Medium Error
[current] [descriptor]
Jan 12 02:15:59 kernel: Descriptor sense data with sense descriptors
(in hex):
Jan 12 02:15:59 kernel: 72 03 11 00 00 00 00 34 00 0a 80 00 00
00 00 01
Jan 12 02:15:59 kernel: cd e3 86 90 01 0a 00 00 00 00 00 00 81
03 01 00
Jan 12 02:15:59 kernel: 02 06 00 00 80 00 ff 00 03 02 00 86 80
0e 00 00
Jan 12 02:15:59 kernel: 00 00 00 00 00 00 00 00 00 00 00 00
Jan 12 02:15:59 kernel: sd 8:0:21:0: [sdcf] Add. Sense: Unrecovered
read error
Jan 12 02:15:59 kernel: sd 8:0:21:0: [sdcf] CDB: Read(16): 88 00 00 00
00 01 cd e3 86 00 00 00 01 00 00 00
Jan 12 02:16:02 kernel: sd 7:0:21:0: [sdx] Unhandled sense code
Jan 12 02:16:02 kernel: sd 7:0:21:0: [sdx] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
Jan 12 02:16:02 kernel: sd 7:0:21:0: [sdx] Sense Key : Medium Error
[current] [descriptor]
Jan 12 02:16:02 kernel: Descriptor sense data with sense descriptors
(in hex):
Jan 12 02:16:02 kernel: 72 03 11 00 00 00 00 34 00 0a 80 00 00
00 00 01
Jan 12 02:16:02 kernel: cd e3 86 90 01 0a 00 00 00 00 00 00 81
03 01 00
Jan 12 02:16:02 kernel: 02 06 00 00 80 00 ff 00 03 02 00 86 80
0e 00 00
Jan 12 02:16:02 kernel: 00 00 00 00 00 00 00 00 00 00 00 00
Jan 12 02:16:02 kernel: sd 7:0:21:0: [sdx] Add. Sense: Unrecovered read
error
Jan 12 02:16:02 kernel: sd 7:0:21:0: [sdx] CDB: Read(16): 88 00 00 00
00 01 cd e3 86 90 00 00 00 70 00 00
Jan 12 02:16:03 kernel: md/raid:md3: read error corrected (8 sectors at
7749205728 on dm-22)
Jan 12 02:16:03 kernel: md/raid:md3: read error corrected (8 sectors at
7749205736 on dm-22)
Jan 12 02:16:03 kernel: md/raid:md3: read error corrected (8 sectors at
7749205744 on dm-22)
Jan 12 02:16:03 kernel: md/raid:md3: read error corrected (8 sectors at
7749205752 on dm-22)
This is all fine and dandy.
We had a case as below and this continued repeatedly for 4 hours until I
logged in and manually failed both paths sdx and sdcf. - (sdx and sdcf
are the same drive). The filesystem running on md3 was hung.Why did the
kernel/mdraid not kick the drive out?
Jan 12 02:38:48 kernel: sd 7:0:21:0: [sdx] Unhandled sense code
Jan 12 02:38:48 kernel: sd 7:0:21:0: [sdx] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
Jan 12 02:38:48 kernel: sd 7:0:21:0: [sdx] Sense Key : Medium Error
[current] [descriptor]
Jan 12 02:38:48 kernel: Descriptor sense data with sense descriptors (in
hex):
Jan 12 02:38:48 kernel: 72 03 16 00 00 00 00 34 00 0a 80 00 00 00
00 01
Jan 12 02:38:48 kernel: d1 53 bd 98 01 0a 00 00 00 00 00 00 86 01
00 00
Jan 12 02:38:48 kernel: 02 06 00 00 80 00 ff 00 03 02 00 80 80 0e
00 00
Jan 12 02:38:48 kernel: 00 00 00 00 00 00 00 00 00 00 00 00
Jan 12 02:38:48 kernel: sd 7:0:21:0: [sdx] Add. Sense: Data
synchronization mark error
Jan 12 02:38:48 kernel: sd 7:0:21:0: [sdx] CDB: Read(16): 88 00 00 00 00
01 d1 53 bd 98 00 00 00 68 00 00
Jan 12 02:38:48 kernel: device-mapper: multipath: Failing path 65:112.
Jan 12 02:38:48 multipathd: 65:112: mark as failed
Jan 12 02:38:48 multipathd: mpathab: remaining active paths: 1
Jan 12 02:38:52 multipathd: mpathab: sdx - directio checker reports path
is up
Jan 12 02:38:52 multipathd: 65:112: reinstated
Jan 12 02:38:52 multipathd: mpathab: remaining active paths: 2
Jan 12 02:39:04 multipathd: 69:48: mark as failed
Jan 12 02:39:04 multipathd: mpathab: remaining active paths: 1
Jan 12 02:39:04 kernel: sd 8:0:21:0: [sdcf] Unhandled sense code
Jan 12 02:39:04 kernel: sd 8:0:21:0: [sdcf] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
Jan 12 02:39:04 kernel: sd 8:0:21:0: [sdcf] Sense Key : Medium Error
[current] [descriptor]
Jan 12 02:39:04 kernel: Descriptor sense data with sense descriptors (in
hex):
Jan 12 02:39:04 kernel: 72 03 16 00 00 00 00 34 00 0a 80 00 00 00
00 01
Jan 12 02:39:04 kernel: d1 53 bd 98 01 0a 00 00 00 00 00 00 86 01
00 00
Jan 12 02:39:04 kernel: 02 06 00 00 80 00 ff 00 03 02 00 80 80 0e
00 00
Jan 12 02:39:04 kernel: 00 00 00 00 00 00 00 00 00 00 00 00
Jan 12 02:39:04 kernel: sd 8:0:21:0: [sdcf] Add. Sense: Data
synchronization mark error
Jan 12 02:39:04 kernel: sd 8:0:21:0: [sdcf] CDB: Read(16): 88 00 00 00
00 01 d1 53 bd 98 00 00 00 68 00 00
Jan 12 02:39:04 kernel: device-mapper: multipath: Failing path 69:48.
Jan 12 02:39:05 multipathd: mpathab: sdcf - directio checker reports
path is up
Jan 12 02:39:05 multipathd: 69:48: reinstated
Jan 12 02:39:05 multipathd: mpathab: remaining active paths: 2
[root@ ~]# rpm -qa | grep multi
device-mapper-multipath-libs-0.4.9-72.el6_5.3.x86_64
device-mapper-multipath-0.4.9-72.el6_5.3.x86_64
[root@ ~]# uname -a
Linux 2.6.32-431.23.3.el6.x86_64 #1 SMP Wed Jul 16 06:12:23 EDT 2014
x86_64 x86_64 x86_64 GNU/Linux
What does "Add. Sense: Data synchronization mark error" mean?
Thanks
^ permalink raw reply
* scsi_debug support
From: Tejas Rao @ 2016-01-15 0:22 UTC (permalink / raw)
To: linux-raid
Are scsi_debug devices supported with linux raid. I cannot seem to
create a basic array.
[root@temp01 ~]# modprobe scsi_debug add_host=2 max_luns=3 num_tgts=4
dev_size_mb=10240
[root@temp01 ~]# lsscsi | grep -e sda -e sdb
[8:2:0:0] disk IBM ServeRAID M5110e 3.34 /dev/sdbm
[8:2:1:0] disk IBM ServeRAID M5110e 3.34 /dev/sdbn
[52:0:0:0] disk Linux scsi_debug 0004 /dev/sda
[52:0:0:1] disk Linux scsi_debug 0004 /dev/sdb
[root@temp01 ~]# fdisk -l /dev/sda
Disk /dev/sda: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 32768 bytes
Disk identifier: 0x00000000
[root@temp01 ~]# mdadm --create --verbose /dev/md0 --level=0
--raid-devices=2 /dev/sda /dev/sdb
mdadm: super1.x cannot open /dev/sda: Device or resource busy
mdmon: ddf: Cannot use /dev/sda: Device or resource busy
mdmon: Cannot use /dev/sda: It is busy
mdadm: cannot open /dev/sda: Device or resource busy
[root@temp01 ~]#
[root@temp01 ~]# mdadm -V
mdadm - v3.3 - 3rd September 2013
[root@temp01 ~]# uname -a
Linux temp01.rcf.bnl.gov 2.6.32-573.12.1.el6.x86_64 #1 SMP Mon Nov 23
12:55:32 EST 2015 x86_64 x86_64 x86_64 GNU/Linux
[root@temp01 ~]#
^ permalink raw reply
* Re: writeback: Stability issue (BUG) on 4.4 with writeback_percent
From: Ming Lei @ 2016-01-15 3:19 UTC (permalink / raw)
To: Ming Lin; +Cc: Miu Vlad-Cosmin, linux-bcache, linux-raid
In-Reply-To: <CAF1ivSY9urc58Ff6axkNrQX8hYxCZNRhAMcH6cEPyyeiBO+=MA@mail.gmail.com>
Cc raid list.
On Fri, Jan 15, 2016 at 1:51 AM, Ming Lin <mlin@kernel.org> wrote:
> On Wed, Jan 13, 2016 at 11:22 PM, Miu Vlad-Cosmin <miuvlad@gmail.com> wrote:
>> Hello,
>>
>> In a rather basic bcache setup (one cache + mdraid backing),
>> I encounter a kernel problem related to bcache with 4.4.0.
>>
>> In order to trigger this bug, fill the cache with some dirty data.
>> When there is some dirty data, wait for the bcache_writeback to
>> start writing it to the backing device (0-3 minutes)
>> and the BUG triggers.
>>
>> Please find more info here: https://bugzilla.kernel.org/show_bug.cgi?id=110771
>>
>> [<ffffffff815822af>] make_request+0x47f/0xca0
>> [<ffffffff815a5d3d>] md_make_request+0xdd/0x220
>> [<ffffffff810c53ce>] ? pick_next_task_fair+0x12e/0x450
>> [<ffffffff81311d2e>] generic_make_request+0xce/0x1b0
>> [<ffffffff815a1b70>] write_dirty+0x60/0xb0
>> [<ffffffff810aafa7>] process_one_work+0x147/0x3d0
>> [<ffffffff810ab546>] worker_thread+0x46/0x440
>> [<ffffffff810ab500>] ? rescuer_thread+0x2d0/0x2d0
>> [<ffffffff810ab500>] ? rescuer_thread+0x2d0/0x2d0
>> [<ffffffff810afeb4>] kthread+0xc4/0xe0
>> [<ffffffff810afdf0>] ? kthread_park+0x50/0x50
>> [<ffffffff8170c85f>] ret_from_fork+0x3f/0x70
>>
>> A bisect shows "[578270bfbd2803dc7b0b03fbc2ac119efbc73195]
>> block: fix segment split" as the problem.
It is the 2nd time to report this commit as 'regression', and last time
it is because bio bounce is after splitting. The commit itself is correct
and the report should be false positive, the real bug might be related
with bio splitting.
> [ 83.436844] BUG: unable to handle kernel NULL pointer dereference at 0000000000000028
> [ 83.437025] IP: [<ffffffff81309ce5>] bio_trim+0x15/0xe0
0028 should be offset of 'bio->bi_iter.bi_size', so looks 'read_bio' from
bio_clone_mddev() is NULL?
BTW, can some write loading trigger the bug just on raid1 without bcache?
Thanks,
>
> CC Ming Lei.
>
>>
>> Anyone can confirm this ?
>>
>> Thanks,
>> Vlad
^ permalink raw reply
* [GIT PULL REQUEST] md updates for 4.5
From: NeilBrown @ 2016-01-15 6:30 UTC (permalink / raw)
To: Linus Torvalds
Cc: LKML, Arnd Bergmann, Christoph Hellwig, Dan Williams,
Deepa Dinamani, Goldwyn Rodrigues, Guoqing Jiang, Mike Snitzer,
Roman Gushchin, Shaohua Li, linux-raid
[-- Attachment #1: Type: text/plain, Size: 2976 bytes --]
The following changes since commit 168309855a7d1e16db751e9c647119fe2d2dc878:
Linux 4.4-rc8 (2016-01-03 15:15:37 -0800)
are available in the git repository at:
git://neil.brown.name/md tags/md/4.5
for you to fetch changes up to 1501efadc524a0c99494b576923091589a52d2a4:
md/raid: only permit hot-add of compatible integrity profiles (2016-01-14 11:49:57 +1100)
----------------------------------------------------------------
md updates for 4.5
Mostly clustered-raid1 and raid5 journal updates.
one Y2038 fix and other minor stuff.
One patch removes me from the MAINTAINERS file and adds a record of
my md maintainership to Credits.
----------------------------------------------------------------
Arnd Bergmann (1):
md: avoid warning for 32-bit sector_t
Christoph Hellwig (5):
raid5-cache: simplify r5l_move_io_unit_list
raid5-cache: free meta_page earlier
raid5-cache: use a bio_set
raid5-cache: use a mempool for the metadata block
raid5: allow r5l_io_unit allocations to fail
Dan Williams (1):
md/raid: only permit hot-add of compatible integrity profiles
Deepa Dinamani (1):
drivers: md: use ktime_get_real_seconds()
Goldwyn Rodrigues (3):
md-cluster: Avoid the resync ping-pong
md-cluster: Fix the remove sequence with the new MD reload code
md-cluster: Allow spare devices to be marked as faulty
Guoqing Jiang (8):
md-cluster: remove a disk asynchronously from cluster environment
md-cluster: append some actions when change bitmap from clustered to none
md-cluster: update the documentation
md-cluster: Defer MD reloading to mddev->thread
md-cluster: Protect communication with mutexes
md-cluster: update comments for MD_CLUSTER_SEND_LOCKED_ALREADY
md: update comment for md_allow_write
md: remove unnecesary md_new_event_inintr
NeilBrown (2):
md: Remove 'ready' field from mddev.
Remove myself as MD Maintainer, and add to Credits.
Roman Gushchin (1):
md/raid5: remove redundant check in stripe_add_to_batch_list()
Shaohua Li (4):
raid5-cache: add journal hot add/remove support
md: set MD_HAS_JOURNAL in correct places
MD: add journal with array suspended
raid5-cache: handle journal hotadd in quiesce
CREDITS | 1 +
Documentation/md-cluster.txt | 314 ++++++++++++++++++++++++++++++-----------
MAINTAINERS | 1 -
drivers/md/md-cluster.c | 164 +++++++++++++++++++--
drivers/md/md-cluster.h | 2 +
drivers/md/md.c | 171 +++++++++++++---------
drivers/md/md.h | 11 +-
drivers/md/multipath.c | 6 +-
drivers/md/raid1.c | 6 +-
drivers/md/raid10.c | 6 +-
drivers/md/raid5-cache.c | 158 ++++++++++++++++-----
drivers/md/raid5.c | 36 +++--
include/uapi/linux/raid/md_u.h | 4 +-
13 files changed, 649 insertions(+), 231 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
^ permalink raw reply
* RE: best base / worst case RAID 5,6 write speeds
From: Robert Kierski @ 2016-01-15 16:53 UTC (permalink / raw)
To: doug@easyco.com; +Cc: linux-raid@vger.kernel.org
In-Reply-To: <CAFx4rwSo3MNqJGNQ3wHe49F+xQ6559aZdikPL4M3+HuD6uRz-Q@mail.gmail.com>
Hey Doug,
I tried as you suggested... only that didn't help. So I actually had to get down into the guts to figure out what was going wrong.
It turned out to be a bug in the block layer of the 3.18 kernel that required a one line change. With that fixed, the FastWrite patch works like a charm.
Thanks!
Bob Kierski
Senior Storage Performance Engineer
Cray Inc.
380 Jackson Street
Suite 210
St. Paul, MN 55101
Tele: 651-967-9590
Fax: 651-605-9001
Cell: 651-890-7461
^ permalink raw reply
* Re: broken raid level 5 array caused by user error
From: Mathias Mueller @ 2016-01-18 15:33 UTC (permalink / raw)
To: Phil Turmel; +Cc: Linux raid, linux-raid-owner
In-Reply-To: <a7d58e8e4c319c320bc531b8d2bf11e7@pingofdeath.de>
Hi Phil,
first thanks a lot for all your help and time you already spent on me
and my problem. I gathered some more information and hope you can help
me a bit more.
I found this on serverfault.com and tried to figure out my raid layout
using some image file that is stored on my raid for sure:
http://serverfault.com/questions/347606/recover-raid-5-data-after-created-new-array-instead-of-re-using
this is my current device mapping:
JK1100YAG64A1T -> sdc
ML0220F30PZUVD -> sdd (this is the disk I added last)
JK1121YAG7YDLS -> sde
JK1170YBHYV6MD -> sdf
First I tried to figure out the chunk size. I used a jpg file that was
stored on the raid for sure and read 8x32 Bytes with an offset of 64k
from that file. Than I used bgrep to search for the bytestrings on my
physical devices. I found five sequent byte strings on one physical
device, so I think the chunk sice must be bigger than 256k.
Because I was pretty sure, that my chunk size is 512k, I was reading
5x32Byte with an offset of 512k from my jpg file, to determine the order
of the devices. After bgrep was done, I got the following results:
- Every bytestring was found 3x on my physical devices, I think it's
because the file is existing 3x in different folders on my raid device
(which is pretty certain, I know that the file is existing 2x at least)
- sdd1 seems to have a different offset as the other physical devices,
it's the disk I added last after switching from debian to centos some
years ago
- the following tables show at which offsets and on which physical
devices the five byte strings have been found:
offset sdc1 sdd1 sde1 sdf1
---------------------------------------------------
5400bd3000 2
5400cc3000 3 1
5400d43000 4 5
offset sdc1 sdd1 sde1 sdf1
---------------------------------------------------
87b4e52000 3
87b4f42000 1 2
87b4fc2000 5 4
offset sdc1 sdd1 sde1 sdf1
---------------------------------------------------
cb2d87f000 2
cb2d96f000 1
cb2d9ef000 4 3 5
So I think using the last table is the easiest one to figure out the
partition order and the data offset between sdd1 and the other devices?
offset sdc1 sdd1 sde1 sdf1
---------------------------------------------------
cb2d96f000 (2) P 1
cb2d9ef000 4 P 3 5
If I am right, it would mean, that the order of my physical devices is
sdf1 sdd1 sde1 sdc1 (without knowing which one is the first partition)
and the offset between sdd1 and the other devices is f0000. Are my
assumptions correct? How can I go on with this information?
Thanks a lot in advance
Best regards
Mathias
^ permalink raw reply
* ICH RAID5 delisted and broken after mdadm installation
From: Пётр Б. @ 2016-01-18 17:10 UTC (permalink / raw)
To: linux-raid
[-- Attachment #1: Type: text/plain, Size: 1487 bytes --]
Hello guys.
sda, sdb and sdd were a RAID5 array with 64K chunk size and were used
in Windows and were always connected to the ICH9r controller in this
order.
HDD containing the Windows (sdb) was failing, Windows crashed severly
and I booted into Debian (from sde) to backup information (BIOS listed
RAID5 volume correctly). I booted into Debian and installed mdadm, I
told it that all drives are needed for boot in the process (not true
atm).
After I installed mdadm no new partitions appeared in Gnome. After I
rebooted I saw in RAID BIOS output that sda and sdb are "offline
members" and that sdc is non-raid (it's true) and that sdd is non-raid
(it's false). Also, no RAID volumes are detected.
/dev/md/imsm0 is a link for /dev/md127 which is empty
/dev/md/imsm1 is a link for /dev/md128 which is empty
mdadm reports that no RAID superblock information was found on sdd.
"mdadm --assemble md0 sda sdb sdd" fails:
>mdadm: cannot open device sda: Device or resource busy
>mdadm: sda has no superblock - assembly aborted
It outputs the same for whhichever HDD I list first - sda, sdb, sdd.
Linux 2.6.32-5-amd64 #1 SMP Sun Dec 21 18:01:12 UTC 2014 x86_64 GNU/Linux
mdadm - v3.1.4 - 31st August 2010
I won't boot into Windows before I fix this. Please give me some tips.
P.S. What was I doing wrong? Except using ICH RAID (which, as I
learned ATM does not even implies additional hardware unit and is no
better than software RAID) and using Windows on a failing drive of
course.
[-- Attachment #2: raid_status --]
[-- Type: application/octet-stream, Size: 2116 bytes --]
sda:
Magic : Intel Raid ISM Cfg Sig.
Version : 1.0.00
Orig Family : 69ee55dc
Family : 69ee55dc
Generation : 0000002f
UUID : 3a35d3bc:76e760fa:18961fb6:79631a32
Checksum : 3ecaf78e correct
MPB Sectors : 1
Disks : 2
RAID Devices : 1
Disk00 Serial : Z4Y725VC
State : active
Id : 00020000
Usable Size : 1953520904 (931.51 GiB 1000.20 GB)
[Volume_0000]:
UUID : 05630097:5c3ca47d:b9278835:03c27bac
RAID Level : 0
Members : 2
Slots : [UU]
This Slot : 0
Array Size : 3907041280 (1863.02 GiB 2000.41 GB)
Per Dev Size : 1953520904 (931.51 GiB 1000.20 GB)
Sector Offset : 0
Num Stripes : 15261880
Chunk Size : 64 KiB
Reserved : 0
Migrate State : idle
Map State : normal
Dirty State : clean
Disk01 Serial : Z4Y82FDE
State : active
Id : 00030000
Usable Size : 1953520904 (931.51 GiB 1000.20 GB)
sdb:
Magic : Intel Raid ISM Cfg Sig.
Version : 1.2.02
Orig Family : 0cb49cd3
Family : 0cb7d1ef
Generation : 00017bba
UUID : 4c95fbd9:97f70aef:b4d7dc43:2bc8345e
Checksum : 5cd59d95 correct
MPB Sectors : 2
Disks : 3
RAID Devices : 1
Disk01 Serial : Z4Y82FDE
State : active
Id : 00030000
Usable Size : 1953520654 (931.51 GiB 1000.20 GB)
[RAID5_64K]:
UUID : b045475e:53e6e056:60eba77d:b826d370
RAID Level : 5
Members : 3
Slots : [UUU]
This Slot : 1
Array Size : 3907035136 (1863.02 GiB 2000.40 GB)
Per Dev Size : 1953517832 (931.51 GiB 1000.20 GB)
Sector Offset : 0
Num Stripes : 15261856
Chunk Size : 64 KiB
Reserved : 0
Migrate State : idle
Map State : normal
Dirty State : clean
Disk00 Serial : Z4Y725VC
State : active
Id : 00020000
Usable Size : 1953518541 (931.51 GiB 1000.20 GB)
Disk02 Serial : 9QJ81RTJ
State : active
Id : 00050000
Usable Size : 1953518541 (931.51 GiB 1000.20 GB)
^ permalink raw reply
* Re: ICH RAID5 delisted and broken after mdadm installation
From: Пётр Б. @ 2016-01-18 17:13 UTC (permalink / raw)
To: linux-raid
In-Reply-To: <CA+Ni7jMa2TSSYbDcZ-HQTp5O42UZ==r7wJ5dikXfytHgHF7pzQ@mail.gmail.com>
I found a mistake: sdc contains Windows and is failing, not sdb.
^ permalink raw reply
* Re: [PATCH 00/35 v3] eparate operations from flags in the bio/request structs
From: Christoph Hellwig @ 2016-01-18 18:15 UTC (permalink / raw)
To: mchristi
Cc: linux-f2fs-devel, linux-ext4, konrad.wilk, drbd-dev,
philipp.reisner, lars.ellenberg, linux-raid, dm-devel,
linux-fsdevel, linux-bcache, linux-block, linux-kernel,
linux-scsi, linux-mtd, target-devel, linux-btrfs, osd-dev, xfs,
ocfs2-devel
In-Reply-To: <1452543693-4440-1-git-send-email-mchristi@redhat.com>
The whole sries looks fine to me:
Reviewed-by: Christoph Hellwig <hch@lst.de>
There are a few pieces of future work on top of this I'd rather see
sooner than later though:
- use REQ_OP_FLUSH for all empty flushes, including those at the bio
level.
- merge the req->cmd_type values into req->op. Right now that's
basically only a new REQ_OP_BLOCK_PC (or better REQ_OP_SCSI while
we're at it) and a REQ_OP_DRV_PRIV as the last value.
- drop as many of the crazy defines based on REQ_* in fs.h (e.g.
(READ_SYNC, WRITE_SYNC, WRITE_ODIRECT, WRITE_FLUSH, WRITE_FUA,
WRITE_FLUSH_FUA, RW_MASK, RWA_MASK)
^ permalink raw reply
* Re: broken raid level 5 array caused by user error
From: Phil Turmel @ 2016-01-18 19:09 UTC (permalink / raw)
To: Mathias Mueller; +Cc: Linux raid, linux-raid-owner
In-Reply-To: <44d28ec402622b25c4d4d7a32a8888d9@pingofdeath.de>
Hi Mathias,
On 01/18/2016 10:33 AM, Mathias Mueller wrote:
> Hi Phil,
>
> first thanks a lot for all your help and time you already spent on me
> and my problem. I gathered some more information and hope you can help
> me a bit more.
You're welcome.
> First I tried to figure out the chunk size. I used a jpg file that was
> stored on the raid for sure and read 8x32 Bytes with an offset of 64k
> from that file. Than I used bgrep to search for the bytestrings on my
> physical devices. I found five sequent byte strings on one physical
> device, so I think the chunk sice must be bigger than 256k.
Very interesting. You could go one step further and compare the jpeg
file contents in the first 1M against the locations found to determine
where the chunks actually start and end on each device. The final
offset will be a chunk multiple before these boundaries. Or do md5 sums
of 4k blocks to reduce the amount to inspect.
> If I am right, it would mean, that the order of my physical devices is
> sdf1 sdd1 sde1 sdc1 (without knowing which one is the first partition)
> and the offset between sdd1 and the other devices is f0000. Are my
> assumptions correct? How can I go on with this information?
This will help (and looks correct), but I don't remember what we did to
try to find the beginning of your filesystem. Did we search for a
filesystem signature? Please re-summarize that.
Phil
^ permalink raw reply
* [PATCH] Abort pending request for RAID10
From: Hannes Reinecke @ 2016-01-19 8:55 UTC (permalink / raw)
To: Neil Brown; +Cc: Shaohua Li, linux-raid, Hannes Reinecke
RAID10 delays the write until the bitmap has been updated.
So it really should check if the device is still working
before sending requests, otherwise it'll happily sending
I/O to a known faulty device.
Signed-off-by: Hannes Reinecke <hare@suse.de>
---
drivers/md/raid10.c | 38 ++++++++++++++++++++++++++++++++++++--
1 file changed, 36 insertions(+), 2 deletions(-)
diff --git a/drivers/md/raid10.c b/drivers/md/raid10.c
index d4efed7..74369c2 100644
--- a/drivers/md/raid10.c
+++ b/drivers/md/raid10.c
@@ -902,12 +902,29 @@ static void flush_pending_writes(struct r10conf *conf)
while (bio) { /* submit pending writes */
struct bio *next = bio->bi_next;
+ struct r10bio *r10_bio = bio->bi_private;
+ struct md_rdev *rdev = NULL;
+ int dev, slot, repl;
bio->bi_next = NULL;
+ dev = find_bio_disk(conf, r10_bio, bio, &slot, &repl);
+ if (repl)
+ rdev = conf->mirrors[dev].replacement;
+ if (!rdev) {
+ smp_rmb();
+ repl = 0;
+ rdev = conf->mirrors[dev].rdev;
+ }
if (unlikely((bio->bi_rw & REQ_DISCARD) &&
!blk_queue_discard(bdev_get_queue(bio->bi_bdev))))
/* Just ignore it */
bio_endio(bio);
- else
+ else if (test_bit(Faulty, &rdev->flags)) {
+ if (test_bit(Timeout, &rdev->flags))
+ bio->bi_error = -ETIMEDOUT;
+ else
+ bio->bi_error = -EIO;
+ bio_endio(bio);
+ } else
generic_make_request(bio);
bio = next;
}
@@ -1079,12 +1096,29 @@ static void raid10_unplug(struct blk_plug_cb *cb, bool from_schedule)
while (bio) { /* submit pending writes */
struct bio *next = bio->bi_next;
+ struct r10bio *r10_bio = bio->bi_private;
+ struct md_rdev *rdev = NULL;
+ int dev, slot, repl;
bio->bi_next = NULL;
+ dev = find_bio_disk(conf, r10_bio, bio, &slot, &repl);
+ if (repl)
+ rdev = conf->mirrors[dev].replacement;
+ if (!rdev) {
+ smp_rmb();
+ repl = 0;
+ rdev = conf->mirrors[dev].rdev;
+ }
if (unlikely((bio->bi_rw & REQ_DISCARD) &&
!blk_queue_discard(bdev_get_queue(bio->bi_bdev))))
/* Just ignore it */
bio_endio(bio);
- else
+ else if (test_bit(Faulty, &rdev->flags)) {
+ if (test_bit(Timeout, &rdev->flags))
+ bio->bi_error = -ETIMEDOUT;
+ else
+ bio->bi_error = -EIO;
+ bio_endio(bio);
+ } else
generic_make_request(bio);
bio = next;
}
--
1.8.5.6
^ permalink raw reply related
* Re: [PATCH] Abort pending request for RAID10
From: kbuild test robot @ 2016-01-19 9:05 UTC (permalink / raw)
Cc: kbuild-all, Neil Brown, Shaohua Li, linux-raid, Hannes Reinecke
In-Reply-To: <1453193726-4617-1-git-send-email-hare@suse.de>
[-- Attachment #1: Type: text/plain, Size: 3293 bytes --]
Hi Hannes,
[auto build test ERROR on v4.4-rc8]
[also build test ERROR on next-20160119]
[if your patch is applied to the wrong git tree, please drop us a note to help improving the system]
url: https://github.com/0day-ci/linux/commits/Hannes-Reinecke/Abort-pending-request-for-RAID10/20160119-165822
config: x86_64-randconfig-x012-01180513 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All error/warnings (new ones prefixed by >>):
In file included from include/asm-generic/bug.h:4:0,
from arch/x86/include/asm/bug.h:35,
from include/linux/bug.h:4,
from include/linux/mmdebug.h:4,
from include/linux/gfp.h:4,
from include/linux/slab.h:14,
from drivers/md/raid10.c:21:
drivers/md/raid10.c: In function 'flush_pending_writes':
>> drivers/md/raid10.c:884:18: error: 'Timeout' undeclared (first use in this function)
if (test_bit(Timeout, &rdev->flags))
^
include/linux/compiler.h:147:28: note: in definition of macro '__trace_if'
if (__builtin_constant_p((cond)) ? !!(cond) : \
^
>> drivers/md/raid10.c:884:5: note: in expansion of macro 'if'
if (test_bit(Timeout, &rdev->flags))
^
>> drivers/md/raid10.c:884:9: note: in expansion of macro 'test_bit'
if (test_bit(Timeout, &rdev->flags))
^
drivers/md/raid10.c:884:18: note: each undeclared identifier is reported only once for each function it appears in
if (test_bit(Timeout, &rdev->flags))
^
include/linux/compiler.h:147:28: note: in definition of macro '__trace_if'
if (__builtin_constant_p((cond)) ? !!(cond) : \
^
>> drivers/md/raid10.c:884:5: note: in expansion of macro 'if'
if (test_bit(Timeout, &rdev->flags))
^
>> drivers/md/raid10.c:884:9: note: in expansion of macro 'test_bit'
if (test_bit(Timeout, &rdev->flags))
^
drivers/md/raid10.c: In function 'raid10_unplug':
drivers/md/raid10.c:1077:17: error: 'Timeout' undeclared (first use in this function)
if (test_bit(Timeout, &rdev->flags))
^
include/linux/compiler.h:147:28: note: in definition of macro '__trace_if'
if (__builtin_constant_p((cond)) ? !!(cond) : \
^
drivers/md/raid10.c:1077:4: note: in expansion of macro 'if'
if (test_bit(Timeout, &rdev->flags))
^
drivers/md/raid10.c:1077:8: note: in expansion of macro 'test_bit'
if (test_bit(Timeout, &rdev->flags))
^
vim +/Timeout +884 drivers/md/raid10.c
878 }
879 if (unlikely((bio->bi_rw & REQ_DISCARD) &&
880 !blk_queue_discard(bdev_get_queue(bio->bi_bdev))))
881 /* Just ignore it */
882 bio_endio(bio);
883 else if (test_bit(Faulty, &rdev->flags)) {
> 884 if (test_bit(Timeout, &rdev->flags))
885 bio->bi_error = -ETIMEDOUT;
886 else
887 bio->bi_error = -EIO;
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 19773 bytes --]
^ permalink raw reply
* Help with RAID data recovery.
From: Tommy Wang @ 2016-01-19 10:17 UTC (permalink / raw)
To: linux-raid
Hi,
I need some help recovering the data on a Synology NAS. There are no backups of
the data (but, you can bet there will be if I recover the data!).
The situation:
7 drives in the NAS: 3x2TB, 2x3TB, 2x4TB. Using Synology Hyrbid Raid (md+lvm2).
I started with 4x2TB, then expanded 1 disk at a time (3TB, 3TB, 4TB, 4TB).
While expanding with the 2nd 4TB, I experienced a failure (I was messing with
the Synology software and it fork bombed itself) and was forced to reboot.
Lesson: leave your system alone during any reshape.
The raid layout prior to expansion of second 4TB disk:
sda sdb sdc sde sdf sdg
2TB 4TB 3TB 3TB 2TB 2TB
md0 (raid1): sda1 sdb1 sdc1 sde1 sdf1 sdg1 (2550 MB/partition)
md1 (raid1): sda2 sdb2 sdc2 sde2 sdf2 sdg2 (2147 MB/partition)
md2 (raid5): sda5 sdb5 sdc5 sde5 sdf5 sdg5 (1995 GB/partition)
md3 (raid5): sdb6 sdc6 sde6 (1000 GB/partition)
Note, that sdb has 1 TB of unpartitioned space.
The raid layout after expansion of second 4TB disk:
sda sdb sdc sdd sde sdf sdg
2TB 4TB 3TB 4TB 3TB 2TB 2TB
md0 (raid1): sda1 sdb1 sdc1 sdd1 sde1 sdf1 sdg1 (2550 MB/partition)
md1 (raid1): sda2 sdb2 sdc2 sdd2 sde2 sdf2 sdg2 (2147 MB/partition)
md2 (raid5): sda5 sdb5 sdc5 sdd5 sde5 sdf5 sdg5 (1995 GB/partition)
md3 (raid5): sdb6 sdc6 sdd6 sde6 (1000 GB/partition)
md4 (raid1): sdb7 sdd7 (1000 GB/partition)
Synology uses md0 as the system partition and md1 as swap. md2, md3, and m4 are
added to a single volume group (vg1000) and creates a single logical volume
(named lv).
After rebooting, I checked mdstat:
/proc/mdstat:
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md2 : active raid5 sda5[0] sdd5[6] sdb5[5] sde5[4] sdc5[3] sdg5[2] sdf5[1]
11692100736 blocks super 1.2 level 5, 64k chunk, algorithm 2 [7/7] [UUUUUUU]
[===========>.........] resync = 55.2% (1076399232/1948683456) finish=208.5min speed=69700K/sec
md4 : active raid1 sdb7[0] sdd7[1]
976742912 blocks super 1.2 [2/2] [UU]
md1 : active raid1 sda2[0] sdb2[1] sdc2[2] sdd2[3] sde2[4] sdf2[5] sdg2[6]
2097088 blocks [12/7] [UUUUUUU_____]
md0 : active raid1 sda1[0] sdb1[5] sdc1[3] sdd1[6] sde1[4] sdf1[1] sdg1[2]
2490176 blocks [12/7] [UUUUUUU_____]
unused devices: <none>
The above log was taken later, but I had actually rebooted it during reshape.
It appears that md2 automatically assembled and resumed reshape and resync. It
also appears that md4 was successfully created. But, where was md3?
Logs from mdadm --detail and --examine are included at the bottom of this email.
I have also included logs from parted -l, as well as /var/log/messages, and
pertinent files from /etc/lvm/backup and /etc/lvm/archive.
I let md2 complete and then left the system alone. Unfortunately, last night I
experienced a power failure and I have not powered it on since.
In order to better understand what was going on, I created a VirtualBox VM to
simulate the failure. I added 3x8GB, 2x10GB, and 2x12GB disks in some random
order to the IDE and a SATA controller on the virtual machine.
After installing Synology, I expanded the disks in the same order I did for the
NAS (8G/8G/8G + 10G + 10G + 12G + 12G), and killed power to the VM during the
expansion of the last 12GB disk.
Here is /proc/mdstat prior to expanding the last disk:
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md3 : active raid5 sdf6[2] sdd6[1] sda6[0]
4174720 blocks super 1.2 level 5, 64k chunk, algorithm 2 [3/3] [UUU]
md2 : active raid5 sdg5[5] sdf5[4] sde5[3] sdd5[2] sdb5[1] sda5[0]
17786560 blocks super 1.2 level 5, 64k chunk, algorithm 2 [6/6] [UUUUUU]
md1 : active raid1 sda2[0] sdb2[1] sdc2[2] sdd2[3] sde2[4] sdf2[5] sdg2[6]
2097088 blocks [12/7] [UUUUUUU_____]
md0 : active raid1 sda1[0] sdb1[1] sdc1[2] sdd1[3] sde1[4] sdf1[5] sdg1[6]
2490176 blocks [12/7] [UUUUUUU_____]
unused devices: <none>
For the VM, sdc was the new disk (it was present when the NAS was installed, so
it is a member of md0 and md1; but, was not included in the initial build of the
md2 array). I put a watch -n 1 'cat /proc/mdstat' and started the last
expansion:
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md4 : active raid1 sdc7[1] sda7[0]
2087360 blocks super 1.2 [2/2] [UU]
md3 : active raid5 sda6[0] sdf6[2] sdd6[1]
4174720 blocks super 1.2 level 5, 64k chunk, algorithm 2 [3/3] [UUU]
md2 : active raid5 sdc5[6] sda5[0] sdg5[5] sdf5[4] sde5[3] sdd5[2] sdb5[1]
17786560 blocks super 1.2 level 5, 64k chunk, algorithm 2 [7/7] [UUUUUUU]
[>....................] reshape = 0.6% (24320/3557312) finish=4.8min speed=12160K/sec
md1 : active raid1 sda2[0] sdb2[1] sdc2[2] sdd2[3] sde2[4] sdf2[5] sdg2[6]
2097088 blocks [12/7] [UUUUUUU_____]
md0 : active raid1 sda1[0] sdb1[1] sdc1[2] sdd1[3] sde1[4] sdf1[5] sdg1[6]
2490176 blocks [12/7] [UUUUUUU_____]
unused devices: <none>
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md4 : active raid1 sdc7[1] sda7[0]
2087360 blocks super 1.2 [2/2] [UU]
md3 : active raid5 sdc6[3] sda6[0] sdf6[2] sdd6[1]
4174720 blocks super 1.2 level 5, 64k chunk, algorithm 2 [4/4] [UUUU]
resync=DELAYED
md2 : active raid5 sdc5[6] sda5[0] sdg5[5] sdf5[4] sde5[3] sdd5[2] sdb5[1]
17786560 blocks super 1.2 level 5, 64k chunk, algorithm 2 [7/7] [UUUUUUU]
[>....................] reshape = 0.8% (30080/3557312) finish=5.8min speed=10026K/sec
md1 : active raid1 sda2[0] sdb2[1] sdc2[2] sdd2[3] sde2[4] sdf2[5] sdg2[6]
2097088 blocks [12/7] [UUUUUUU_____]
md0 : active raid1 sda1[0] sdb1[1] sdc1[2] sdd1[3] sde1[4] sdf1[5] sdg1[6]
2490176 blocks [12/7] [UUUUUUU_____]
unused devices: <none>
Notice that:
* md4 was created from sdc7 and sda7
* md3 was converted to a 4-disk raid5, but resync=DELAYED
* md2 was converted to a 7-disk raid5 and is currently performing a reshape
My guess is that Synology performed all actions against the RAID devices, but
allowed mdadm to perform reshape/resync one device at a time. I assume that
Synology next continuously polls mdstat, and when finished, will perform the
vgextend/lvextend actions.
Upon powering on the VM again, I inspected mdstat again:
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md4 : active raid1 sda7[0] sdc7[1]
2087360 blocks super 1.2 [2/2] [UU]
md2 : active raid5 sda5[0] sdc5[6] sdg5[5] sdf5[4] sde5[3] sdd5[2] sdb5[1]
17786560 blocks super 1.2 level 5, 64k chunk, algorithm 2 [7/7] [UUUUUUU]
[==>..................] reshape = 13.7% (489056/3557312) finish=3.9min speed=13013K/sec
md1 : active raid1 sda2[0] sdb2[1] sdc2[2] sdd2[3] sde2[4] sdf2[5] sdg2[6]
2097088 blocks [12/7] [UUUUUUU_____]
md0 : active raid1 sda1[0] sdb1[1] sdc1[2] sdd1[3] sde1[4] sdf1[5] sdg1[6]
2490176 blocks [12/7] [UUUUUUU_____]
unused devices: <none>
Much like my real NAS, md2 resumed reshape/resync, md3 disappeared, and md4 was
created and is clean.
At this point, I tried to reassemble md3, but got stuck because I didn't have a
backup-file (even though the Reshape pos'n was 0). It would just say:
mdadm: Failed to restore critical section for reshape, sorry.
Possibly you needed to specify the --backup-file
Assuming md3 was not touched at all other than perhaps metadata for the raid
configuration, I reasoned that I should be able to just recreate the array in
the configuration prior to expansion. The output mdadm -A --scan --verbose
shows me that /dev/sd[adfc] were slots 0-3 for md3. Assuming that the new
partition is slot 3, I tried to re-create the array with the first 3 devices:
size=$(( $(mdadm --examine /dev/sda6 | grep Used | tr -s ' ' | cut -d' ' -f6) / 2 ))
mdadm --create --assume-clean --level=5 --raid-devices=3 --size=$size /dev/md3 /dev/sd[adf]6
vgchange -a y
mount /dev/vg1000/lv /mnt
And, voila! My data is there. I ran some quick CRC-32 and SHA-1 sums on my
test data and they all match.
UPDATE:
I tried re-creating the array with all four disks as well:
size=$(( $(mdadm --examine /dev/sda6 | grep Used | tr -s ' ' | cut -d' ' -f6) / 2 ))
mdadm --create --assume-clean --level=5 --raid-devices=4 --size=$size /dev/md3 /dev/sd[adfc]6
vgchange -a y
mount /dev/vg1000/lv /mnt
This also appears to work.
The main questions are:
1. Can I expect to follow the same procedure to recover my data on my NAS?
2. Is there a safer way to recover the data than re-creating the array?
The linux-raid wiki says that recreating the array should be the *last*
resort. I have read other people ask for help with data recovery, and a
common response is to STOP and email this list.
3. Does the order of the devices matter (/dev/sd[adfc]6) matter in the mdadm
--create command? I am infering the order from mdadm -A --scan --verbose but
it appears that the array is successfully created in the right order
regardless of the order I pass in my arguments.
4. Should I recover with 3-disks or 4-disks? Both seemed to work, and the
4-disk variant did not list the last disk as "spare" -- it was active.
I did try the other advice on the wiki (as well as other Internet sources), but
the version of mdadm does not support --invalid-backup, nor does it support
--update=revert-reshape. I could not get an overlay working, as anytime I tried
to add a disk to use as an overlay, it would completely rename the devices
(which I read is a no-no). I also tried booting with a rescue CD to try to get
a newer version of mdadm, but that also renamed everything (my md devices showed
up as /dev/md126, /dev/md127, etc).
Thanks in advance!
Below are logs:
[parted -l]
Model: ATA WDC WD20EARX-00P (scsi)
Disk /dev/hda: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 2551MB 2550MB primary raid
2 2551MB 4699MB 2147MB primary raid
3 4832MB 2000GB 1996GB extended lba
5 4840MB 2000GB 1995GB logical raid
Model: WDC WD20EARX-00PASB0 (scsi)
Disk /dev/sda: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 2551MB 2550MB primary raid
2 2551MB 4699MB 2147MB primary raid
3 4832MB 2000GB 1996GB extended lba
5 4840MB 2000GB 1995GB logical raid
Model: ATA ST4000DM000-1F21 (scsi)
Disk /dev/sdb: 4001GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 2551MB 2550MB ext4 raid
2 2551MB 4699MB 2147MB linux-swap(v1) raid
5 4840MB 2000GB 1995GB raid
6 2000GB 3000GB 1000GB raid
7 3000GB 4001GB 1000GB raid
Model: ATA ST3000DM001-1ER1 (scsi)
Disk /dev/sdc: 3001GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 2551MB 2550MB ext4 raid
2 2551MB 4699MB 2147MB linux-swap(v1) raid
5 4840MB 2000GB 1995GB raid
6 2000GB 3000GB 1000GB raid
Model: ATA ST4000DM000-1F21 (scsi)
Disk /dev/sdd: 4001GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 2551MB 2550MB ext4 raid
2 2551MB 4699MB 2147MB linux-swap(v1) raid
5 4840MB 2000GB 1995GB raid
6 2000GB 3000GB 1000GB raid
7 3000GB 4001GB 1000GB raid
Model: ATA ST3000DM001-1CH1 (scsi)
Disk /dev/sde: 3001GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 2551MB 2550MB ext4 raid
2 2551MB 4699MB 2147MB linux-swap(v1) raid
5 4840MB 2000GB 1995GB raid
6 2000GB 3000GB 1000GB raid
Model: WDC WD20EARS-00S8B1 (scsi)
Disk /dev/sdf: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 2551MB 2550MB primary raid
2 2551MB 4699MB 2147MB primary raid
3 4832MB 2000GB 1996GB extended lba
5 4840MB 2000GB 1995GB logical raid
Model: Linux Software RAID Array (md)
Disk /dev/md0: 2550MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags:
Number Start End Size File system Flags
1 0.00B 2550MB 2550MB ext4
Model: Linux Software RAID Array (md)
Disk /dev/md1: 2147MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags:
Number Start End Size File system Flags
1 0.00B 2147MB 2147MB linux-swap(v1)
Model: Linux Software RAID Array (md)
Disk /dev/md2: 12.0TB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:
Model: Linux Software RAID Array (md)
Disk /dev/md4: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:
Model: WDC WD20EARS-00MVWB0 (scsi)
Disk /dev/sdg: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 2551MB 2550MB primary raid
2 2551MB 4699MB 2147MB primary raid
3 4832MB 2000GB 1996GB extended lba
5 4840MB 2000GB 1995GB logical raid
[madm --examine /dev/sd?1]
/dev/sda1:
Magic : a92b4efc
Version : 0.90.00
UUID : ed28b380:6ad04214:3017a5a8:c86610be
Creation Time : Thu Dec 31 09:42:30 2015
Raid Level : raid1
Used Dev Size : 2490176 (2.37 GiB 2.55 GB)
Array Size : 2490176 (2.37 GiB 2.55 GB)
Raid Devices : 12
Total Devices : 7
Preferred Minor : 0
Update Time : Sun Jan 17 13:11:30 2016
State : clean
Active Devices : 7
Working Devices : 7
Failed Devices : 5
Spare Devices : 0
Checksum : a6f58618 - correct
Events : 404046
Number Major Minor RaidDevice State
this 0 8 1 0 active sync /dev/sda1
0 0 8 1 0 active sync /dev/sda1
1 1 8 81 1 active sync /dev/sdf1
2 2 8 97 2 active sync /dev/sdg1
3 3 8 33 3 active sync /dev/sdc1
4 4 8 65 4 active sync /dev/sde1
5 5 8 17 5 active sync /dev/sdb1
6 6 8 49 6 active sync /dev/sdd1
7 7 0 0 7 faulty removed
8 8 0 0 8 faulty removed
9 9 0 0 9 faulty removed
10 10 0 0 10 faulty removed
11 11 0 0 11 faulty removed
/dev/sdb1:
Magic : a92b4efc
Version : 0.90.00
UUID : ed28b380:6ad04214:3017a5a8:c86610be
Creation Time : Thu Dec 31 09:42:30 2015
Raid Level : raid1
Used Dev Size : 2490176 (2.37 GiB 2.55 GB)
Array Size : 2490176 (2.37 GiB 2.55 GB)
Raid Devices : 12
Total Devices : 7
Preferred Minor : 0
Update Time : Sun Jan 17 13:11:30 2016
State : clean
Active Devices : 7
Working Devices : 7
Failed Devices : 5
Spare Devices : 0
Checksum : a6f58632 - correct
Events : 404046
Number Major Minor RaidDevice State
this 5 8 17 5 active sync /dev/sdb1
0 0 8 1 0 active sync /dev/sda1
1 1 8 81 1 active sync /dev/sdf1
2 2 8 97 2 active sync /dev/sdg1
3 3 8 33 3 active sync /dev/sdc1
4 4 8 65 4 active sync /dev/sde1
5 5 8 17 5 active sync /dev/sdb1
6 6 8 49 6 active sync /dev/sdd1
7 7 0 0 7 faulty removed
8 8 0 0 8 faulty removed
9 9 0 0 9 faulty removed
10 10 0 0 10 faulty removed
11 11 0 0 11 faulty removed
/dev/sdc1:
Magic : a92b4efc
Version : 0.90.00
UUID : ed28b380:6ad04214:3017a5a8:c86610be
Creation Time : Thu Dec 31 09:42:30 2015
Raid Level : raid1
Used Dev Size : 2490176 (2.37 GiB 2.55 GB)
Array Size : 2490176 (2.37 GiB 2.55 GB)
Raid Devices : 12
Total Devices : 7
Preferred Minor : 0
Update Time : Sun Jan 17 13:11:30 2016
State : clean
Active Devices : 7
Working Devices : 7
Failed Devices : 5
Spare Devices : 0
Checksum : a6f5863e - correct
Events : 404046
Number Major Minor RaidDevice State
this 3 8 33 3 active sync /dev/sdc1
0 0 8 1 0 active sync /dev/sda1
1 1 8 81 1 active sync /dev/sdf1
2 2 8 97 2 active sync /dev/sdg1
3 3 8 33 3 active sync /dev/sdc1
4 4 8 65 4 active sync /dev/sde1
5 5 8 17 5 active sync /dev/sdb1
6 6 8 49 6 active sync /dev/sdd1
7 7 0 0 7 faulty removed
8 8 0 0 8 faulty removed
9 9 0 0 9 faulty removed
10 10 0 0 10 faulty removed
11 11 0 0 11 faulty removed
/dev/sdd1:
Magic : a92b4efc
Version : 0.90.00
UUID : ed28b380:6ad04214:3017a5a8:c86610be
Creation Time : Thu Dec 31 09:42:30 2015
Raid Level : raid1
Used Dev Size : 2490176 (2.37 GiB 2.55 GB)
Array Size : 2490176 (2.37 GiB 2.55 GB)
Raid Devices : 12
Total Devices : 7
Preferred Minor : 0
Update Time : Sun Jan 17 13:11:30 2016
State : clean
Active Devices : 7
Working Devices : 7
Failed Devices : 5
Spare Devices : 0
Checksum : a6f58654 - correct
Events : 404046
Number Major Minor RaidDevice State
this 6 8 49 6 active sync /dev/sdd1
0 0 8 1 0 active sync /dev/sda1
1 1 8 81 1 active sync /dev/sdf1
2 2 8 97 2 active sync /dev/sdg1
3 3 8 33 3 active sync /dev/sdc1
4 4 8 65 4 active sync /dev/sde1
5 5 8 17 5 active sync /dev/sdb1
6 6 8 49 6 active sync /dev/sdd1
7 7 0 0 7 faulty removed
8 8 0 0 8 faulty removed
9 9 0 0 9 faulty removed
10 10 0 0 10 faulty removed
11 11 0 0 11 faulty removed
/dev/sde1:
Magic : a92b4efc
Version : 0.90.00
UUID : ed28b380:6ad04214:3017a5a8:c86610be
Creation Time : Thu Dec 31 09:42:30 2015
Raid Level : raid1
Used Dev Size : 2490176 (2.37 GiB 2.55 GB)
Array Size : 2490176 (2.37 GiB 2.55 GB)
Raid Devices : 12
Total Devices : 7
Preferred Minor : 0
Update Time : Sun Jan 17 13:11:30 2016
State : clean
Active Devices : 7
Working Devices : 7
Failed Devices : 5
Spare Devices : 0
Checksum : a6f58660 - correct
Events : 404046
Number Major Minor RaidDevice State
this 4 8 65 4 active sync /dev/sde1
0 0 8 1 0 active sync /dev/sda1
1 1 8 81 1 active sync /dev/sdf1
2 2 8 97 2 active sync /dev/sdg1
3 3 8 33 3 active sync /dev/sdc1
4 4 8 65 4 active sync /dev/sde1
5 5 8 17 5 active sync /dev/sdb1
6 6 8 49 6 active sync /dev/sdd1
7 7 0 0 7 faulty removed
8 8 0 0 8 faulty removed
9 9 0 0 9 faulty removed
10 10 0 0 10 faulty removed
11 11 0 0 11 faulty removed
/dev/sdf1:
Magic : a92b4efc
Version : 0.90.00
UUID : ed28b380:6ad04214:3017a5a8:c86610be
Creation Time : Thu Dec 31 09:42:30 2015
Raid Level : raid1
Used Dev Size : 2490176 (2.37 GiB 2.55 GB)
Array Size : 2490176 (2.37 GiB 2.55 GB)
Raid Devices : 12
Total Devices : 7
Preferred Minor : 0
Update Time : Sun Jan 17 13:11:30 2016
State : clean
Active Devices : 7
Working Devices : 7
Failed Devices : 5
Spare Devices : 0
Checksum : a6f5866a - correct
Events : 404046
Number Major Minor RaidDevice State
this 1 8 81 1 active sync /dev/sdf1
0 0 8 1 0 active sync /dev/sda1
1 1 8 81 1 active sync /dev/sdf1
2 2 8 97 2 active sync /dev/sdg1
3 3 8 33 3 active sync /dev/sdc1
4 4 8 65 4 active sync /dev/sde1
5 5 8 17 5 active sync /dev/sdb1
6 6 8 49 6 active sync /dev/sdd1
7 7 0 0 7 faulty removed
8 8 0 0 8 faulty removed
9 9 0 0 9 faulty removed
10 10 0 0 10 faulty removed
11 11 0 0 11 faulty removed
/dev/sdg1:
Magic : a92b4efc
Version : 0.90.00
UUID : ed28b380:6ad04214:3017a5a8:c86610be
Creation Time : Thu Dec 31 09:42:30 2015
Raid Level : raid1
Used Dev Size : 2490176 (2.37 GiB 2.55 GB)
Array Size : 2490176 (2.37 GiB 2.55 GB)
Raid Devices : 12
Total Devices : 7
Preferred Minor : 0
Update Time : Sun Jan 17 13:11:30 2016
State : clean
Active Devices : 7
Working Devices : 7
Failed Devices : 5
Spare Devices : 0
Checksum : a6f5867c - correct
Events : 404046
Number Major Minor RaidDevice State
this 2 8 97 2 active sync /dev/sdg1
0 0 8 1 0 active sync /dev/sda1
1 1 8 81 1 active sync /dev/sdf1
2 2 8 97 2 active sync /dev/sdg1
3 3 8 33 3 active sync /dev/sdc1
4 4 8 65 4 active sync /dev/sde1
5 5 8 17 5 active sync /dev/sdb1
6 6 8 49 6 active sync /dev/sdd1
7 7 0 0 7 faulty removed
8 8 0 0 8 faulty removed
9 9 0 0 9 faulty removed
10 10 0 0 10 faulty removed
11 11 0 0 11 faulty removed
[mdadm --examine /dev/sd?2]
/dev/sda2:
Magic : a92b4efc
Version : 0.90.00
UUID : d74ec230:ea7269c6:0d6fa14f:d3c5b4e4 (local to host G530)
Creation Time : Mon Jan 11 18:23:11 2016
Raid Level : raid1
Used Dev Size : 2097088 (2048.28 MiB 2147.42 MB)
Array Size : 2097088 (2048.28 MiB 2147.42 MB)
Raid Devices : 12
Total Devices : 7
Preferred Minor : 1
Update Time : Sun Jan 17 13:12:28 2016
State : clean
Active Devices : 7
Working Devices : 7
Failed Devices : 5
Spare Devices : 0
Checksum : f9720367 - correct
Events : 56
Number Major Minor RaidDevice State
this 0 8 2 0 active sync /dev/sda2
0 0 8 2 0 active sync /dev/sda2
1 1 8 18 1 active sync /dev/sdb2
2 2 8 34 2 active sync /dev/sdc2
3 3 8 50 3 active sync /dev/sdd2
4 4 8 66 4 active sync /dev/sde2
5 5 8 82 5 active sync /dev/sdf2
6 6 8 98 6 active sync /dev/sdg2
7 7 0 0 7 faulty removed
8 8 0 0 8 faulty removed
9 9 0 0 9 faulty removed
10 10 0 0 10 faulty removed
11 11 0 0 11 faulty removed
/dev/sdb2:
Magic : a92b4efc
Version : 0.90.00
UUID : d74ec230:ea7269c6:0d6fa14f:d3c5b4e4 (local to host G530)
Creation Time : Mon Jan 11 18:23:11 2016
Raid Level : raid1
Used Dev Size : 2097088 (2048.28 MiB 2147.42 MB)
Array Size : 2097088 (2048.28 MiB 2147.42 MB)
Raid Devices : 12
Total Devices : 7
Preferred Minor : 1
Update Time : Sun Jan 17 13:12:28 2016
State : clean
Active Devices : 7
Working Devices : 7
Failed Devices : 5
Spare Devices : 0
Checksum : f9720379 - correct
Events : 56
Number Major Minor RaidDevice State
this 1 8 18 1 active sync /dev/sdb2
0 0 8 2 0 active sync /dev/sda2
1 1 8 18 1 active sync /dev/sdb2
2 2 8 34 2 active sync /dev/sdc2
3 3 8 50 3 active sync /dev/sdd2
4 4 8 66 4 active sync /dev/sde2
5 5 8 82 5 active sync /dev/sdf2
6 6 8 98 6 active sync /dev/sdg2
7 7 0 0 7 faulty removed
8 8 0 0 8 faulty removed
9 9 0 0 9 faulty removed
10 10 0 0 10 faulty removed
11 11 0 0 11 faulty removed
/dev/sdc2:
Magic : a92b4efc
Version : 0.90.00
UUID : d74ec230:ea7269c6:0d6fa14f:d3c5b4e4 (local to host G530)
Creation Time : Mon Jan 11 18:23:11 2016
Raid Level : raid1
Used Dev Size : 2097088 (2048.28 MiB 2147.42 MB)
Array Size : 2097088 (2048.28 MiB 2147.42 MB)
Raid Devices : 12
Total Devices : 7
Preferred Minor : 1
Update Time : Sun Jan 17 13:12:28 2016
State : clean
Active Devices : 7
Working Devices : 7
Failed Devices : 5
Spare Devices : 0
Checksum : f972038b - correct
Events : 56
Number Major Minor RaidDevice State
this 2 8 34 2 active sync /dev/sdc2
0 0 8 2 0 active sync /dev/sda2
1 1 8 18 1 active sync /dev/sdb2
2 2 8 34 2 active sync /dev/sdc2
3 3 8 50 3 active sync /dev/sdd2
4 4 8 66 4 active sync /dev/sde2
5 5 8 82 5 active sync /dev/sdf2
6 6 8 98 6 active sync /dev/sdg2
7 7 0 0 7 faulty removed
8 8 0 0 8 faulty removed
9 9 0 0 9 faulty removed
10 10 0 0 10 faulty removed
11 11 0 0 11 faulty removed
/dev/sdd2:
Magic : a92b4efc
Version : 0.90.00
UUID : d74ec230:ea7269c6:0d6fa14f:d3c5b4e4 (local to host G530)
Creation Time : Mon Jan 11 18:23:11 2016
Raid Level : raid1
Used Dev Size : 2097088 (2048.28 MiB 2147.42 MB)
Array Size : 2097088 (2048.28 MiB 2147.42 MB)
Raid Devices : 12
Total Devices : 7
Preferred Minor : 1
Update Time : Sun Jan 17 13:12:28 2016
State : clean
Active Devices : 7
Working Devices : 7
Failed Devices : 5
Spare Devices : 0
Checksum : f972039d - correct
Events : 56
Number Major Minor RaidDevice State
this 3 8 50 3 active sync /dev/sdd2
0 0 8 2 0 active sync /dev/sda2
1 1 8 18 1 active sync /dev/sdb2
2 2 8 34 2 active sync /dev/sdc2
3 3 8 50 3 active sync /dev/sdd2
4 4 8 66 4 active sync /dev/sde2
5 5 8 82 5 active sync /dev/sdf2
6 6 8 98 6 active sync /dev/sdg2
7 7 0 0 7 faulty removed
8 8 0 0 8 faulty removed
9 9 0 0 9 faulty removed
10 10 0 0 10 faulty removed
11 11 0 0 11 faulty removed
/dev/sde2:
Magic : a92b4efc
Version : 0.90.00
UUID : d74ec230:ea7269c6:0d6fa14f:d3c5b4e4 (local to host G530)
Creation Time : Mon Jan 11 18:23:11 2016
Raid Level : raid1
Used Dev Size : 2097088 (2048.28 MiB 2147.42 MB)
Array Size : 2097088 (2048.28 MiB 2147.42 MB)
Raid Devices : 12
Total Devices : 7
Preferred Minor : 1
Update Time : Sun Jan 17 13:12:28 2016
State : clean
Active Devices : 7
Working Devices : 7
Failed Devices : 5
Spare Devices : 0
Checksum : f97203af - correct
Events : 56
Number Major Minor RaidDevice State
this 4 8 66 4 active sync /dev/sde2
0 0 8 2 0 active sync /dev/sda2
1 1 8 18 1 active sync /dev/sdb2
2 2 8 34 2 active sync /dev/sdc2
3 3 8 50 3 active sync /dev/sdd2
4 4 8 66 4 active sync /dev/sde2
5 5 8 82 5 active sync /dev/sdf2
6 6 8 98 6 active sync /dev/sdg2
7 7 0 0 7 faulty removed
8 8 0 0 8 faulty removed
9 9 0 0 9 faulty removed
10 10 0 0 10 faulty removed
11 11 0 0 11 faulty removed
/dev/sdf2:
Magic : a92b4efc
Version : 0.90.00
UUID : d74ec230:ea7269c6:0d6fa14f:d3c5b4e4 (local to host G530)
Creation Time : Mon Jan 11 18:23:11 2016
Raid Level : raid1
Used Dev Size : 2097088 (2048.28 MiB 2147.42 MB)
Array Size : 2097088 (2048.28 MiB 2147.42 MB)
Raid Devices : 12
Total Devices : 7
Preferred Minor : 1
Update Time : Sun Jan 17 13:12:28 2016
State : clean
Active Devices : 7
Working Devices : 7
Failed Devices : 5
Spare Devices : 0
Checksum : f97203c1 - correct
Events : 56
Number Major Minor RaidDevice State
this 5 8 82 5 active sync /dev/sdf2
0 0 8 2 0 active sync /dev/sda2
1 1 8 18 1 active sync /dev/sdb2
2 2 8 34 2 active sync /dev/sdc2
3 3 8 50 3 active sync /dev/sdd2
4 4 8 66 4 active sync /dev/sde2
5 5 8 82 5 active sync /dev/sdf2
6 6 8 98 6 active sync /dev/sdg2
7 7 0 0 7 faulty removed
8 8 0 0 8 faulty removed
9 9 0 0 9 faulty removed
10 10 0 0 10 faulty removed
11 11 0 0 11 faulty removed
/dev/sdg2:
Magic : a92b4efc
Version : 0.90.00
UUID : d74ec230:ea7269c6:0d6fa14f:d3c5b4e4 (local to host G530)
Creation Time : Mon Jan 11 18:23:11 2016
Raid Level : raid1
Used Dev Size : 2097088 (2048.28 MiB 2147.42 MB)
Array Size : 2097088 (2048.28 MiB 2147.42 MB)
Raid Devices : 12
Total Devices : 7
Preferred Minor : 1
Update Time : Sun Jan 17 13:12:28 2016
State : clean
Active Devices : 7
Working Devices : 7
Failed Devices : 5
Spare Devices : 0
Checksum : f97203d3 - correct
Events : 56
Number Major Minor RaidDevice State
this 6 8 98 6 active sync /dev/sdg2
0 0 8 2 0 active sync /dev/sda2
1 1 8 18 1 active sync /dev/sdb2
2 2 8 34 2 active sync /dev/sdc2
3 3 8 50 3 active sync /dev/sdd2
4 4 8 66 4 active sync /dev/sde2
5 5 8 82 5 active sync /dev/sdf2
6 6 8 98 6 active sync /dev/sdg2
7 7 0 0 7 faulty removed
8 8 0 0 8 faulty removed
9 9 0 0 9 faulty removed
10 10 0 0 10 faulty removed
11 11 0 0 11 faulty removed
[mdadm --examine /dev/sd?5]
/dev/sda5:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : ea9a241d:1482b49d:5ea11c87:e689bdf0
Name : G530:2 (local to host G530)
Creation Time : Thu Dec 31 09:58:51 2015
Raid Level : raid5
Raid Devices : 7
Avail Dev Size : 3897366912 (1858.41 GiB 1995.45 GB)
Array Size : 23384201472 (11150.46 GiB 11972.71 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : active
Device UUID : 48540530:5319c3ff:053851e3:4ae0a358
Update Time : Sun Jan 17 13:11:02 2016
Checksum : 66a27c76 - correct
Events : 39119
Layout : left-symmetric
Chunk Size : 64K
Device Role : Active device 0
Array State : AAAAAAA ('A' == active, '.' == missing)
/dev/sdb5:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : ea9a241d:1482b49d:5ea11c87:e689bdf0
Name : G530:2 (local to host G530)
Creation Time : Thu Dec 31 09:58:51 2015
Raid Level : raid5
Raid Devices : 7
Avail Dev Size : 3897366912 (1858.41 GiB 1995.45 GB)
Array Size : 23384201472 (11150.46 GiB 11972.71 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : active
Device UUID : ef97a20f:01900be1:552d9a54:d7bf0662
Update Time : Sun Jan 17 13:11:02 2016
Checksum : a2340bac - correct
Events : 39119
Layout : left-symmetric
Chunk Size : 64K
Device Role : Active device 5
Array State : AAAAAAA ('A' == active, '.' == missing)
/dev/sdc5:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : ea9a241d:1482b49d:5ea11c87:e689bdf0
Name : G530:2 (local to host G530)
Creation Time : Thu Dec 31 09:58:51 2015
Raid Level : raid5
Raid Devices : 7
Avail Dev Size : 3897366912 (1858.41 GiB 1995.45 GB)
Array Size : 23384201472 (11150.46 GiB 11972.71 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : active
Device UUID : e60d53a3:e106cc0b:1435aa89:10876e49
Update Time : Sun Jan 17 13:11:02 2016
Checksum : 7d1cc779 - correct
Events : 39119
Layout : left-symmetric
Chunk Size : 64K
Device Role : Active device 3
Array State : AAAAAAA ('A' == active, '.' == missing)
/dev/sdd5:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : ea9a241d:1482b49d:5ea11c87:e689bdf0
Name : G530:2 (local to host G530)
Creation Time : Thu Dec 31 09:58:51 2015
Raid Level : raid5
Raid Devices : 7
Avail Dev Size : 3897366912 (1858.41 GiB 1995.45 GB)
Array Size : 23384201472 (11150.46 GiB 11972.71 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : active
Device UUID : 22d4e109:a3c1e226:9a7ebfe6:005d9ca3
Update Time : Sun Jan 17 13:11:02 2016
Checksum : b60567f0 - correct
Events : 39119
Layout : left-symmetric
Chunk Size : 64K
Device Role : Active device 6
Array State : AAAAAAA ('A' == active, '.' == missing)
/dev/sde5:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : ea9a241d:1482b49d:5ea11c87:e689bdf0
Name : G530:2 (local to host G530)
Creation Time : Thu Dec 31 09:58:51 2015
Raid Level : raid5
Raid Devices : 7
Avail Dev Size : 3897366912 (1858.41 GiB 1995.45 GB)
Array Size : 23384201472 (11150.46 GiB 11972.71 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : active
Device UUID : a08b2485:0f2efd4e:645a20f8:16dcde68
Update Time : Sun Jan 17 13:11:02 2016
Checksum : 3005e6b9 - correct
Events : 39119
Layout : left-symmetric
Chunk Size : 64K
Device Role : Active device 4
Array State : AAAAAAA ('A' == active, '.' == missing)
/dev/sdf5:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : ea9a241d:1482b49d:5ea11c87:e689bdf0
Name : G530:2 (local to host G530)
Creation Time : Thu Dec 31 09:58:51 2015
Raid Level : raid5
Raid Devices : 7
Avail Dev Size : 3897366912 (1858.41 GiB 1995.45 GB)
Array Size : 23384201472 (11150.46 GiB 11972.71 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : active
Device UUID : 5d021082:54485b2c:4644bd82:454656fa
Update Time : Sun Jan 17 13:11:02 2016
Checksum : 2663cbc9 - correct
Events : 39119
Layout : left-symmetric
Chunk Size : 64K
Device Role : Active device 1
Array State : AAAAAAA ('A' == active, '.' == missing)
/dev/sdg5:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : ea9a241d:1482b49d:5ea11c87:e689bdf0
Name : G530:2 (local to host G530)
Creation Time : Thu Dec 31 09:58:51 2015
Raid Level : raid5
Raid Devices : 7
Avail Dev Size : 3897366912 (1858.41 GiB 1995.45 GB)
Array Size : 23384201472 (11150.46 GiB 11972.71 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : active
Device UUID : 53c65dfd:49e8d483:c0fb21a3:7ccf5336
Update Time : Sun Jan 17 13:11:02 2016
Checksum : 558d7066 - correct
Events : 39119
Layout : left-symmetric
Chunk Size : 64K
Device Role : Active device 2
Array State : AAAAAAA ('A' == active, '.' == missing)
[mdadm --examine /dev/sd?6]
/dev/sdb6:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x4
Array UUID : 7a711117:6923feb5:189dd236:a4588ccb
Name : G530:3 (local to host G530)
Creation Time : Sun Jan 10 14:42:24 2016
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 1953485856 (931.49 GiB 1000.18 GB)
Array Size : 5860457472 (2794.48 GiB 3000.55 GB)
Used Dev Size : 1953485824 (931.49 GiB 1000.18 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : cf7de3ce:9870bc53:10996640:fecad7fe
Reshape pos'n : 0
Delta Devices : 1 (3->4)
Update Time : Sat Jan 16 04:00:42 2016
Checksum : 9ffe27fd - correct
Events : 2662
Layout : left-symmetric
Chunk Size : 64K
Device Role : Active device 2
Array State : AAAA ('A' == active, '.' == missing)
/dev/sdc6:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x4
Array UUID : 7a711117:6923feb5:189dd236:a4588ccb
Name : G530:3 (local to host G530)
Creation Time : Sun Jan 10 14:42:24 2016
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 1953485856 (931.49 GiB 1000.18 GB)
Array Size : 5860457472 (2794.48 GiB 3000.55 GB)
Used Dev Size : 1953485824 (931.49 GiB 1000.18 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 689fe836:76c74e90:fb6af582:1fc460b9
Reshape pos'n : 0
Delta Devices : 1 (3->4)
Update Time : Sat Jan 16 04:00:42 2016
Checksum : 41ad6b7e - correct
Events : 2662
Layout : left-symmetric
Chunk Size : 64K
Device Role : Active device 0
Array State : AAAA ('A' == active, '.' == missing)
/dev/sdd6:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x4
Array UUID : 7a711117:6923feb5:189dd236:a4588ccb
Name : G530:3 (local to host G530)
Creation Time : Sun Jan 10 14:42:24 2016
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 1953485856 (931.49 GiB 1000.18 GB)
Array Size : 5860457472 (2794.48 GiB 3000.55 GB)
Used Dev Size : 1953485824 (931.49 GiB 1000.18 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : bed228eb:31257f54:c2aa00d7:063375f1
Reshape pos'n : 0
Delta Devices : 1 (3->4)
Update Time : Sat Jan 16 04:00:42 2016
Checksum : 463dab41 - correct
Events : 2662
Layout : left-symmetric
Chunk Size : 64K
Device Role : Active device 3
Array State : AAAA ('A' == active, '.' == missing)
/dev/sde6:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x4
Array UUID : 7a711117:6923feb5:189dd236:a4588ccb
Name : G530:3 (local to host G530)
Creation Time : Sun Jan 10 14:42:24 2016
Raid Level : raid5
Raid Devices : 4
Avail Dev Size : 1953485856 (931.49 GiB 1000.18 GB)
Array Size : 5860457472 (2794.48 GiB 3000.55 GB)
Used Dev Size : 1953485824 (931.49 GiB 1000.18 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 6a627079:cfb96d7c:4ab53bf4:c92ca522
Reshape pos'n : 0
Delta Devices : 1 (3->4)
Update Time : Sat Jan 16 04:00:42 2016
Checksum : 4aded3d3 - correct
Events : 2662
Layout : left-symmetric
Chunk Size : 64K
Device Role : Active device 1
Array State : AAAA ('A' == active, '.' == missing)
[mdadm --examine /dev/sd?7]
/dev/sdb7:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : 80224e42:05546401:c3cc4e39:177c3cb1
Name : G530:4 (local to host G530)
Creation Time : Sat Jan 16 04:00:36 2016
Raid Level : raid1
Raid Devices : 2
Avail Dev Size : 1953485856 (931.49 GiB 1000.18 GB)
Array Size : 1953485824 (931.49 GiB 1000.18 GB)
Used Dev Size : 1953485824 (931.49 GiB 1000.18 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 914b86e5:34498dc9:4319a930:c8ce2e06
Update Time : Sun Jan 17 02:57:27 2016
Checksum : 82df11db - correct
Events : 2
Device Role : Active device 0
Array State : AA ('A' == active, '.' == missing)
/dev/sdd7:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : 80224e42:05546401:c3cc4e39:177c3cb1
Name : G530:4 (local to host G530)
Creation Time : Sat Jan 16 04:00:36 2016
Raid Level : raid1
Raid Devices : 2
Avail Dev Size : 1953485856 (931.49 GiB 1000.18 GB)
Array Size : 1953485824 (931.49 GiB 1000.18 GB)
Used Dev Size : 1953485824 (931.49 GiB 1000.18 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
State : clean
Device UUID : 075d1bd6:f89b5714:41c9b39a:9a8fe9a2
Update Time : Sun Jan 17 02:57:27 2016
Checksum : c503e6e6 - correct
Events : 2
Device Role : Active device 1
Array State : AA ('A' == active, '.' == missing)
[mdadm --detail /dev/md[0124]
/dev/md0:
Version : 0.90
Creation Time : Thu Dec 31 09:42:30 2015
Raid Level : raid1
Array Size : 2490176 (2.37 GiB 2.55 GB)
Used Dev Size : 2490176 (2.37 GiB 2.55 GB)
Raid Devices : 12
Total Devices : 7
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Sun Jan 17 13:16:37 2016
State : clean, degraded
Active Devices : 7
Working Devices : 7
Failed Devices : 0
Spare Devices : 0
UUID : ed28b380:6ad04214:3017a5a8:c86610be
Events : 0.404128
Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 81 1 active sync /dev/sdf1
2 8 97 2 active sync /dev/sdg1
3 8 33 3 active sync /dev/sdc1
4 8 65 4 active sync /dev/sde1
5 8 17 5 active sync /dev/sdb1
6 8 49 6 active sync /dev/sdd1
7 0 0 7 removed
8 0 0 8 removed
9 0 0 9 removed
10 0 0 10 removed
11 0 0 11 removed
/dev/md1:
Version : 0.90
Creation Time : Mon Jan 11 18:23:11 2016
Raid Level : raid1
Array Size : 2097088 (2048.28 MiB 2147.42 MB)
Used Dev Size : 2097088 (2048.28 MiB 2147.42 MB)
Raid Devices : 12
Total Devices : 7
Preferred Minor : 1
Persistence : Superblock is persistent
Update Time : Sun Jan 17 13:12:28 2016
State : clean, degraded
Active Devices : 7
Working Devices : 7
Failed Devices : 0
Spare Devices : 0
UUID : d74ec230:ea7269c6:0d6fa14f:d3c5b4e4 (local to host G530)
Events : 0.56
Number Major Minor RaidDevice State
0 8 2 0 active sync /dev/sda2
1 8 18 1 active sync /dev/sdb2
2 8 34 2 active sync /dev/sdc2
3 8 50 3 active sync /dev/sdd2
4 8 66 4 active sync /dev/sde2
5 8 82 5 active sync /dev/sdf2
6 8 98 6 active sync /dev/sdg2
7 0 0 7 removed
8 0 0 8 removed
9 0 0 9 removed
10 0 0 10 removed
11 0 0 11 removed
/dev/md2:
Version : 1.2
Creation Time : Thu Dec 31 09:58:51 2015
Raid Level : raid5
Array Size : 11692100736 (11150.46 GiB 11972.71 GB)
Used Dev Size : 1948683456 (1858.41 GiB 1995.45 GB)
Raid Devices : 7
Total Devices : 7
Persistence : Superblock is persistent
Update Time : Sun Jan 17 13:16:02 2016
State : active, resyncing
Active Devices : 7
Working Devices : 7
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 64K
Rebuild Status : 54% complete
Name : G530:2 (local to host G530)
UUID : ea9a241d:1482b49d:5ea11c87:e689bdf0
Events : 39120
Number Major Minor RaidDevice State
0 8 5 0 active sync /dev/sda5
1 8 85 1 active sync /dev/sdf5
2 8 101 2 active sync /dev/sdg5
3 8 37 3 active sync /dev/sdc5
4 8 69 4 active sync /dev/sde5
5 8 21 5 active sync /dev/sdb5
6 8 53 6 active sync /dev/sdd5
/dev/md4:
Version : 1.2
Creation Time : Sat Jan 16 04:00:36 2016
Raid Level : raid1
Array Size : 976742912 (931.49 GiB 1000.18 GB)
Used Dev Size : 976742912 (931.49 GiB 1000.18 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent
Update Time : Sun Jan 17 02:57:27 2016
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Name : G530:4 (local to host G530)
UUID : 80224e42:05546401:c3cc4e39:177c3cb1
Events : 2
Number Major Minor RaidDevice State
0 8 23 0 active sync /dev/sdb7
1 8 55 1 active sync /dev/sdd7
[mdadm -A --scan --verbose]
mdadm: looking for devices for further assembly
mdadm: no recogniseable superblock on 135:241
mdadm: no recogniseable superblock on /dev/synoboot
mdadm: no recogniseable superblock on /dev/md2
mdadm: no recogniseable superblock on /dev/md4
mdadm: cannot open device /dev/zram1: Device or resource busy
mdadm: cannot open device /dev/zram0: Device or resource busy
mdadm: cannot open device /dev/md1: Device or resource busy
mdadm: cannot open device /dev/md0: Device or resource busy
mdadm: cannot open device /dev/sda5: Device or resource busy
mdadm: no recogniseable superblock on /dev/sda3
mdadm: cannot open device /dev/sda2: Device or resource busy
mdadm: cannot open device /dev/sda1: Device or resource busy
mdadm: cannot open device /dev/sda: Device or resource busy
mdadm: cannot open device /dev/sdb7: Device or resource busy
mdadm: cannot open device /dev/sdb5: Device or resource busy
mdadm: cannot open device /dev/sdb2: Device or resource busy
mdadm: cannot open device /dev/sdb1: Device or resource busy
mdadm: cannot open device /dev/sdb: Device or resource busy
mdadm: cannot open device /dev/sdd7: Device or resource busy
mdadm: cannot open device /dev/sdd5: Device or resource busy
mdadm: cannot open device /dev/sdd2: Device or resource busy
mdadm: cannot open device /dev/sdd1: Device or resource busy
mdadm: cannot open device /dev/sdd: Device or resource busy
mdadm: cannot open device /dev/sde5: Device or resource busy
mdadm: cannot open device /dev/sde2: Device or resource busy
mdadm: cannot open device /dev/sde1: Device or resource busy
mdadm: cannot open device /dev/sde: Device or resource busy
mdadm: cannot open device /dev/sdc5: Device or resource busy
mdadm: cannot open device /dev/sdc2: Device or resource busy
mdadm: cannot open device /dev/sdc1: Device or resource busy
mdadm: cannot open device /dev/sdc: Device or resource busy
mdadm: cannot open device /dev/sdg5: Device or resource busy
mdadm: no RAID superblock on /dev/sdg3
mdadm: cannot open device /dev/sdg2: Device or resource busy
mdadm: cannot open device /dev/sdg1: Device or resource busy
mdadm: cannot open device /dev/sdg: Device or resource busy
mdadm: cannot open device /dev/sdf5: Device or resource busy
mdadm: no RAID superblock on /dev/sdf3
mdadm: cannot open device /dev/sdf2: Device or resource busy
mdadm: cannot open device /dev/sdf1: Device or resource busy
mdadm: cannot open device /dev/sdf: Device or resource busy
mdadm: /dev/md/3 exists - ignoring
mdadm: /dev/sdb6 is identified as a member of /dev/md3, slot 2.
mdadm: /dev/sdd6 is identified as a member of /dev/md3, slot 3.
mdadm: /dev/sde6 is identified as a member of /dev/md3, slot 1.
mdadm: /dev/sdc6 is identified as a member of /dev/md3, slot 0.
mdadm:/dev/md3 has an active reshape - checking if critical section needs to be restored
mdadm: No backup metadata on device-3
mdadm: Failed to find backup of critical section
mdadm: Failed to restore critical section for reshape, sorry.
Possibly you needed to specify the --backup-file
mdadm: looking for devices for further assembly
mdadm: no recogniseable superblock on /dev/sdg3
mdadm: no recogniseable superblock on /dev/sdf3
mdadm: No arrays found in config file or automatically
[/var/log/messages - after reboot]
Jan 16 21:10:30 G530 kernel: [ 11.998218] 3ware 9000 Storage Controller device driver for Linux v2.26.02.014.
Jan 16 21:10:30 G530 kernel: [ 12.110889] md: invalid raid superblock magic on sda5
Jan 16 21:10:30 G530 kernel: [ 12.110894] md: sda5 does not have a valid v0.90 superblock, not importing!
Jan 16 21:10:30 G530 kernel: [ 12.161769] md: invalid raid superblock magic on sdb5
Jan 16 21:10:30 G530 kernel: [ 12.161774] md: sdb5 does not have a valid v0.90 superblock, not importing!
Jan 16 21:10:30 G530 kernel: [ 12.181722] md: invalid raid superblock magic on sdb6
Jan 16 21:10:30 G530 kernel: [ 12.181727] md: sdb6 does not have a valid v0.90 superblock, not importing!
Jan 16 21:10:30 G530 kernel: [ 12.200509] md: invalid raid superblock magic on sdb7
Jan 16 21:10:30 G530 kernel: [ 12.200513] md: sdb7 does not have a valid v0.90 superblock, not importing!
Jan 16 21:10:30 G530 kernel: [ 12.244320] md: invalid raid superblock magic on sdc5
Jan 16 21:10:30 G530 kernel: [ 12.244325] md: sdc5 does not have a valid v0.90 superblock, not importing!
Jan 16 21:10:30 G530 kernel: [ 12.264668] md: invalid raid superblock magic on sdc6
Jan 16 21:10:30 G530 kernel: [ 12.264673] md: sdc6 does not have a valid v0.90 superblock, not importing!
Jan 16 21:10:30 G530 kernel: [ 12.312386] md: invalid raid superblock magic on sdd5
Jan 16 21:10:30 G530 kernel: [ 12.312391] md: sdd5 does not have a valid v0.90 superblock, not importing!
Jan 16 21:10:30 G530 kernel: [ 12.331066] md: invalid raid superblock magic on sdd6
Jan 16 21:10:30 G530 kernel: [ 12.331070] md: sdd6 does not have a valid v0.90 superblock, not importing!
Jan 16 21:10:30 G530 kernel: [ 12.347779] md: invalid raid superblock magic on sdd7
Jan 16 21:10:30 G530 kernel: [ 12.347783] md: sdd7 does not have a valid v0.90 superblock, not importing!
Jan 16 21:10:30 G530 kernel: [ 12.381133] md: invalid raid superblock magic on sde5
Jan 16 21:10:30 G530 kernel: [ 12.381138] md: sde5 does not have a valid v0.90 superblock, not importing!
Jan 16 21:10:30 G530 kernel: [ 12.400495] md: invalid raid superblock magic on sde6
Jan 16 21:10:30 G530 kernel: [ 12.400499] md: sde6 does not have a valid v0.90 superblock, not importing!
Jan 16 21:10:30 G530 kernel: [ 12.456511] md: invalid raid superblock magic on sdf5
Jan 16 21:10:30 G530 kernel: [ 12.456515] md: sdf5 does not have a valid v0.90 superblock, not importing!
Jan 16 21:10:30 G530 kernel: [ 12.504338] md: invalid raid superblock magic on sdg5
Jan 16 21:10:30 G530 kernel: [ 12.504342] md: sdg5 does not have a valid v0.90 superblock, not importing!
Jan 16 21:10:30 G530 kernel: [ 12.504371] md: sda2 has different UUID to sda1
Jan 16 21:10:30 G530 kernel: [ 12.504375] md: sdb2 has different UUID to sda1
Jan 16 21:10:30 G530 kernel: [ 12.504379] md: sdc2 has different UUID to sda1
Jan 16 21:10:30 G530 kernel: [ 12.504383] md: sdd2 has different UUID to sda1
Jan 16 21:10:30 G530 kernel: [ 12.504387] md: sde2 has different UUID to sda1
Jan 16 21:10:30 G530 kernel: [ 12.504391] md: sdf2 has different UUID to sda1
Jan 16 21:10:30 G530 kernel: [ 12.504395] md: sdg2 has different UUID to sda1
Jan 16 21:10:30 G530 kernel: [ 12.647433] Warning! ehci_hcd should always be loaded before uhci_hcd and ohci_hcd, not after
Jan 16 21:10:30 G530 kernel: [ 12.726663] bromolow_synobios: module license 'Synology Inc.' taints kernel.
Jan 16 21:10:30 G530 kernel: [ 12.726666] Disabling lock debugging due to kernel taint
Jan 16 21:10:30 G530 kernel: [ 12.727077] 2016-1-17 3:10:20 UTC
Jan 16 21:10:30 G530 kernel: [ 12.727083] Brand: Synology
Jan 16 21:10:30 G530 kernel: [ 12.727085] Model: DS-3615xs
Jan 16 21:10:30 G530 kernel: [ 12.727087] set group disks wakeup number to 4, spinup time deno 7
Jan 16 21:10:30 G530 kernel: [ 13.120649] Got empty serial number. Generate serial number from product.
Jan 16 21:10:30 G530 kernel: [ 13.237986] synobios: unload
Jan 16 21:10:30 G530 kernel: [ 13.380869] Got empty serial number. Generate serial number from product.
Jan 16 21:10:30 G530 kernel: [ 13.380881] drivers/usb/core/hub.c (2674) Same device found. Change serial to ffffffd1ffffffb2ffffffdbffffffa0
Jan 16 21:10:30 G530 kernel: [ 15.471362] Got empty serial number. Generate serial number from product.
Jan 16 21:10:30 G530 kernel: [ 15.471372] drivers/usb/core/hub.c (2674) Same device found. Change serial to ffffffd1ffffffb2ffffffdbffffffa0
Jan 16 21:10:30 G530 kernel: [ 15.471374] drivers/usb/core/hub.c (2674) Same device found. Change serial to ffffffd1ffffffb2ffffffdbffffffa1
Jan 16 21:10:30 G530 kernel: [ 16.055404] EXT4-fs (md0): synoacl module has not been loaded. Unable to mount with synoacl, vfs_mod status=-1
Jan 16 21:10:30 G530 kernel: [ 16.767872] Got empty serial number. Generate serial number from product.
Jan 16 21:10:30 G530 kernel: [ 16.767883] drivers/usb/core/hub.c (2674) Same device found. Change serial to ffffffd1ffffffb2ffffffdbffffffa0
Jan 16 21:10:30 G530 kernel: [ 16.767885] drivers/usb/core/hub.c (2674) Same device found. Change serial to ffffffd1ffffffb2ffffffdbffffffa1
Jan 16 21:10:30 G530 kernel: [ 16.767886] drivers/usb/core/hub.c (2674) Same device found. Change serial to ffffffd1ffffffb2ffffffdbffffffa2
Jan 16 21:10:30 G530 kernel: [ 16.768045] usb 3-3.4: ep 0x81 - rounding interval to 1024 microframes, ep desc says 2040 microframes
Jan 16 21:10:30 G530 kernel: [ 18.093256] Got empty serial number. Generate serial number from product.
Jan 16 21:10:30 G530 kernel: [ 18.093392] usb 3-3.4.1: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
Jan 16 21:10:30 G530 kernel: [ 18.093397] usb 3-3.4.1: ep 0x82 - rounding interval to 64 microframes, ep desc says 80 microframes
Jan 16 21:10:30 G530 kernel: [ 18.093400] usb 3-3.4.1: ep 0x83 - rounding interval to 32 microframes, ep desc says 40 microframes
Jan 16 21:10:30 G530 kernel: [ 20.844390] EXT4-fs (md0): synoacl module has not been loaded. Unable to mount with synoacl, vfs_mod status=-1
Creating /dev/synoboot1...
Creating /dev/synoboot2...
Jan 16 21:10:33 G530 umount: can't umount /initrd: Invalid argument
Jan 16 21:10:35 G530 kernel: [ 27.827659] zram: module is from the staging directory, the quality is unknown, you have been warned.
Jan 16 21:10:35 G530 [ 27.916922] init: syno-auth-check main process (14182) killed by TERM signal
Jan 16 21:10:35 G530 kernel: [ 28.347530] thermal_sys: exports duplicate symbol get_thermal_instance (owned by kernel)
insmod: can't insert '/lib/modules/thermal_sys.ko': invalid module format
Jan 16 21:10:35 G530 kernel: [ 28.396328] processor: exports duplicate symbol acpi_processor_get_bios_limit (owned by kernel)
insmod: can't insert '/lib/modules/processor.ko': invalid module format
insmod: can't insert '/lib/modules/aesni-intel.ko': No such device
Jan 16 21:10:35 G530 kernel: [ 28.608051] i2c_algo_bit: exports duplicate symbol i2c_bit_add_bus (owned by kernel)
insmod: can't insert '/lib/modules/i2c-algo-bit.ko': invalid module format
Jan 16 21:10:36 G530 kernel: [ 28.741219] 2016-1-17 3:10:36 UTC
Jan 16 21:10:36 G530 kernel: [ 28.741227] Brand: Synology
Jan 16 21:10:36 G530 kernel: [ 28.741229] Model: DS-3615xs
Jan 16 21:10:36 G530 kernel: [ 28.741231] set group disks wakeup number to 4, spinup time deno 7
Jan 16 21:10:36 G530 synonetseqadj: synonetseqadj.c:312 Error internal NIC devices 1 does not equal to internal NIC number 4
Jan 16 21:10:37 G530 interface-catcher: eth0 (dhcp) is added
Jan 16 21:10:37 G530 interface-catcher: lo (inet 127.0.0.1 netmask 255.0.0.0 ) is added
Jan 16 21:10:38 G530 synonetd: net_route_table_edit.c:72 eth0 ip route del failed, instead of route
Jan 16 21:10:39 G530 dhcp-client: started on eth0
Jan 16 21:10:39 G530 [ 31.943766] init: dhcp-client (eth0) main process (18275) killed by TERM signal
Jan 16 21:10:39 G530 dhcp-client: stopped on eth0
Jan 16 21:10:39 G530 dhcp-client: started on eth0
Jan 16 21:10:39 G530 spacetool.shared: spacetool.c:1069 Try to force assemble RAID [/dev/md3]. [0x8000 raid_ioctl_info.c:55]
Jan 16 21:10:39 G530 spacetool.shared: raid_allow_rmw_check.c:48 fopen failed: /usr/syno/etc/.rmw.md4
Jan 16 21:10:39 G530 kernel: [ 32.529366] md: md2: current auto_remap = 0
Jan 16 21:10:39 G530 kernel: [ 32.529368] md: reshape of RAID array md2
Jan 16 21:10:39 G530 spacetool.shared: raid_allow_rmw_check.c:48 fopen failed: /usr/syno/etc/.rmw.md2
Jan 16 21:10:40 G530 spacetool.shared: raid_allow_rmw_check.c:35 Failed to get RAID '/dev/md3' info.
Jan 16 21:10:40 G530 spacetool.shared: raid_enable_multithread.c:42 Failed to get RAID '/dev/md3' info.
Jan 16 21:10:40 G530 spacetool.shared: spacetool.c:1097 Fail to enable multithread of [/dev/md3]
Jan 16 21:10:42 G530 [ 34.826762] init: dhcp-client (eth0) main process (18642) killed by TERM signal
Jan 16 21:10:42 G530 dhcp-client: stopped on eth0
Jan 16 21:10:42 G530 dhcp-client: started on eth0
Jan 16 21:10:44 G530 synonetd: servicecfg_internal_lib.c:355 skip reload stopping/stopped job [ddnsd][0xD300 servicectl_job_reload.c:42]
Jan 16 21:10:45 G530 spacetool.shared: spacetool.c:2835 [Info] Old vg path: [/dev/vg1000], New vg path: [/dev/vg1000], UUID: [OJ3oNy-SLGN-RvdT-KLiG-jDs2-JbxB-4ommso]
Jan 16 21:10:45 G530 spacetool.shared: spacetool.c:2842 [Info] Activate all VG
Jan 16 21:10:46 G530 ddnsd: ddnsd.c:2912 DDNS Expired. UpdateAll.
Jan 16 21:10:47 G530 spacetool.shared: lvm_vg_activate.c:23 Failed to do '/sbin/vgchange -ay /dev/vg1000'
Jan 16 21:10:47 G530 spacetool.shared: spacetool.c:2851 Failed to activate LVM [/dev/vg1000]
Jan 16 21:10:47 G530 spacetool.shared: spacetool.c:2896 space: [/dev/vg1000]
Jan 16 21:10:47 G530 spacetool.shared: spacetool.c:2922 space: [/dev/vg1000], ndisk: [9]
Jan 16 21:10:47 G530 ddnsd: ddnsd.c:1968 Success to update [all.dnsomatic.com] with IP [72.64.92.20] at [DNS-O-Matic]
Jan 16 21:10:51 G530 spacetool.shared: space_map_file_dump.c:1440 Fail to get lv UUID: [/dev/vg1000/lv]
Jan 16 21:10:51 G530 spacetool.shared: space_map_file_dump.c:1251 Fail to get pv expansible: [/dev/md4]
Jan 16 21:10:51 G530 spacetool.shared: space_map_file_dump.c:1251 Fail to get pv expansible: [/dev/md2]
Jan 16 21:10:53 G530 synovspace: virtual_space_conf_check.c:78 [INFO] "PASS" checking configuration of virtual space [FCACHE], app: [1]
Jan 16 21:10:53 G530 synovspace: virtual_space_conf_check.c:74 [INFO] No implementation, skip checking configuration of virtual space [HA]
Jan 16 21:10:53 G530 synovspace: virtual_space_conf_check.c:74 [INFO] No implementation, skip checking configuration of virtual space [SNAPSHOT_ORG]
Jan 16 21:10:53 G530 synovspace: vspace_wrapper_load_all.c:76 [INFO] No virtual layer above space: [/volume1] / [/dev/vg1000/lv]
Jan 16 21:10:54 G530 s00_synocheckfstab: system_blk_dev_readahead_set.c:36 Failed to set '/dev/vg1000/lv''s readahead to 4096d
Jan 16 21:10:54 G530 s00_synocheckfstab: volume_readahead_allset.c:33 Failed to set RA on [/dev/vg1000/lv]
mount: open failed, msg:No such file or directory
mount: mounting /dev/vg1000/lv on /volume1 failed: No such device
mv: can't rename '/volume1/@tmp': No such file or directory
quotacheck: Mountpoint (or device) /volume1 not found or has no quota enabled.
quotacheck: Cannot find filesystem to check or filesystem not mounted with quota option.
quotaon: Mountpoint (or device) /volume1 not found or has no quota enabled.
Jan 16 21:10:54 G530 synocheckhotspare: synocheckhotspare.c:149 [INFO] No hotspare config, skip hotspare config check. [0x2000 virtual_space_layer_get.c:98]
Jan 16 21:10:54 G530 rc.ha: ha related packages check
Jan 16 21:10:54 G530 rc.ha: ha related packages check status 0
Jan 16 21:10:55 G530 kernel: [ 48.252145] Get empty minor:104
Jan 16 21:10:55 G530 kernel: [ 48.254034] Get empty minor:105
Jan 16 21:10:55 G530 syno_hdd_util: Model:[WD20EARS-00MVWB0], Firmware:[51.0AB51], S/N:[WD-WMAZA4913001] in [/dev/sdg] is not ssd
Jan 16 21:10:55 G530 syno_hdd_util: Model:[WD20EARS-00S8B1], Firmware:[80.00A80], S/N:[WD-WCAVY5659881] in [/dev/sdf] is not ssd
Jan 16 21:10:55 G530 syno_hdd_util: Model:[ST3000DM001-1CH166], Firmware:[CC46], S/N:[Z1F3MY6N] in [/dev/sde] is not ssd
Jan 16 21:10:55 G530 syno_hdd_util: Model:[ST4000DM000-1F2168], Firmware:[CC54], S/N:[Z303MC89] in [/dev/sdd] is not ssd
Jan 16 21:10:55 G530 syno_hdd_util: Model:[ST3000DM001-1ER166], Firmware:[CC25], S/N:[Z500QP6V] in [/dev/sdc] is not ssd
Jan 16 21:10:56 G530 syno_hdd_util: Model:[ST4000DM000-1F2168], Firmware:[CC54], S/N:[Z3038CR3] in [/dev/sdb] is not ssd
Jan 16 21:10:56 G530 syno_hdd_util: Model:[WD20EARX-00PASB0], Firmware:[51.0AB51], S/N:[WD-WMAZA7147895] in [/dev/sda] is not ssd
Jan 16 21:10:56 G530 synocheckshare: synocheckshare_sync_conf.c:373 Remove Share config: anime / /volume1/anime
Jan 16 21:10:56 G530 synocheckshare: synocheckshare_sync_conf.c:373 Remove Share config: homes / /volume1/homes
Jan 16 21:10:56 G530 synocheckshare: synocheckshare_sync_conf.c:373 Remove Share config: movies / /volume1/movies
Jan 16 21:10:56 G530 synocheckshare: synocheckshare_sync_conf.c:373 Remove Share config: old backups / /volume1/old backups
Jan 16 21:10:56 G530 synocheckshare: synocheckshare_sync_conf.c:373 Remove Share config: photo / /volume1/photo
Jan 16 21:10:56 G530 synocheckshare: synocheckshare_sync_conf.c:373 Remove Share config: Plex / /volume1/Plex
Jan 16 21:10:56 G530 synocheckshare: synocheckshare_sync_conf.c:373 Remove Share config: surveillance / /volume1/surveillance
Jan 16 21:10:56 G530 synocheckshare: synocheckshare_sync_conf.c:373 Remove Share config: tv / /volume1/tv
Jan 16 21:10:57 G530 kernel: [ 49.942850] BUG: unable to handle kernel paging request at 0000000000002ea9
Jan 16 21:10:57 G530 kernel: [ 49.942855] IP: [<ffffffff813d8af7>] syno_mv_9235_disk_led_set+0x27/0xd0
Jan 16 21:10:57 G530 kernel: [ 49.942861] PGD 2146d0067 PUD 2127c4067 PMD 0
Jan 16 21:10:57 G530 kernel: [ 49.942864] Oops: 0000 [#1] SMP
Jan 16 21:10:57 G530 kernel: [ 49.942941] CPU: 0 PID: 21066 Comm: scemd Tainted: P C O 3.10.35 #1
Jan 16 21:10:57 G530 kernel: [ 49.942943] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H77M, BIOS P1.00 03/06/2012
Jan 16 21:10:57 G530 kernel: [ 49.942945] task: ffff880213bef200 ti: ffff8801ff324000 task.ti: ffff8801ff324000
Jan 16 21:10:57 G530 kernel: [ 49.942946] RIP: 0010:[<ffffffff813d8af7>] [<ffffffff813d8af7>] syno_mv_9235_disk_led_set+0x27/0xd0
Jan 16 21:10:57 G530 kernel: [ 49.942950] RSP: 0018:ffff8801ff327d18 EFLAGS: 00010202
Jan 16 21:10:57 G530 kernel: [ 49.942951] RAX: ffff8802127ca000 RBX: 0000000000000000 RCX: ffff8802127ca3e8
Jan 16 21:10:57 G530 kernel: [ 49.942952] RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffff8802127ca000
Jan 16 21:10:57 G530 kernel: [ 49.942953] RBP: 0000000000000000 R08: ffff88020b94a3f8 R09: 0000000000000009
Jan 16 21:10:57 G530 kernel: [ 49.942955] R10: 00000000f773b430 R11: 0000000000000000 R12: ffff88020b94a3c0
Jan 16 21:10:57 G530 kernel: [ 49.942956] R13: 000000000000000b R14: 0000000000000001 R15: 0000000000000000
Jan 16 21:10:57 G530 kernel: [ 49.942957] FS: 0000000000000000(0000) GS:ffff88021f200000(0063) knlGS:00000000f4995b70
Jan 16 21:10:57 G530 kernel: [ 49.942959] CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
Jan 16 21:10:57 G530 kernel: [ 49.942960] CR2: 0000000000002ea9 CR3: 000000020ba74000 CR4: 00000000000407f0
Jan 16 21:10:57 G530 kernel: [ 49.942961] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Jan 16 21:10:57 G530 kernel: [ 49.942963] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Jan 16 21:10:57 G530 synousbdisk: RCClean succeeded
Jan 16 21:10:57 G530 kernel: [ 49.942964] Stack:
Jan 16 21:10:57 G530 kernel: [ 49.942965] 0000000000000007 ffffffffa0af0b98 ffffffffffffffff 00000000f4995048
Jan 16 21:10:57 G530 kernel: [ 49.942967] ffff88020b94a3c0 ffffffffa0aed574 00000000f6f92000 ffff8801ff327de0
Jan 16 21:10:57 G530 kernel: [ 49.942969] ffff880211505000 0000000000000008 00000000ffffff9c 00000000ffffff9c
Jan 16 21:10:57 G530 kernel: [ 49.942971] Call Trace:
Jan 16 21:10:57 G530 kernel: [ 49.942976] [<ffffffffa0af0b98>] ? SetSCSIHostLedStatusBy9235GPIOandAHCISGPIO+0x68/0x100 [bromolow_synobios]
Jan 16 21:10:57 G530 kernel: [ 49.942980] [<ffffffffa0aed574>] ? synobios_ioctl+0xe24/0x1060 [bromolow_synobios]
Jan 16 21:10:57 G530 kernel: [ 49.942984] [<ffffffff8110c26c>] ? filename_lookup+0x2c/0xb0
Jan 16 21:10:57 G530 kernel: [ 49.942986] [<ffffffff8110a464>] ? getname_flags.part.31+0x84/0x130
Jan 16 21:10:57 G530 kernel: [ 49.942989] [<ffffffff811111c0>] ? user_path_at_empty+0xa0/0x120
Jan 16 21:10:57 G530 kernel: [ 49.942993] [<ffffffff8116b3fb>] ? sysfs_getattr+0x4b/0x60
Jan 16 21:10:57 G530 kernel: [ 49.942995] [<ffffffff81117b32>] ? dput+0x22/0x1b0
Jan 16 21:10:57 G530 kernel: [ 49.942999] [<ffffffff8114c807>] ? compat_sys_ioctl+0x1e7/0x1500
Jan 16 21:10:57 G530 kernel: [ 49.943003] [<ffffffff810348e0>] ? sys32_stat64+0x10/0x30
Jan 16 21:10:57 G530 kernel: [ 49.943007] [<ffffffff81537a9c>] ? sysenter_dispatch+0x7/0x21
Jan 16 21:10:57 G530 kernel: [ 49.943008] Code: 1f 44 00 00 53 0f b7 ff 89 f3 e8 d5 73 f9 ff 48 85 c0 48 89 c7 0f 84 a0 00 00 00 48 8b 90 68 06 00 00 48 85 d2 0f 84 97 00 00 00 <48> 8b 82 a8 2e 00 00 8b 4a 24 48 8b 70 78 48 8b 40 20 83 c1 04
Jan 16 21:10:57 G530 kernel: [ 49.943028] RIP [<ffffffff813d8af7>] syno_mv_9235_disk_led_set+0x27/0xd0
Jan 16 21:10:57 G530 kernel: [ 49.943031] RSP <ffff8801ff327d18>
Jan 16 21:10:57 G530 kernel: [ 49.943032] CR2: 0000000000002ea9
Jan 16 21:10:57 G530 kernel: [ 49.943034] ---[ end trace 64d42d5492de5895 ]---
Jan 16 21:10:57 G530 synosata: synosata.c:71 no external sata devices granted
Jan 16 21:10:59 G530 hotplugd: hotplugd.c:1274 ##### ACTION:add
Jan 16 21:10:59 G530 hotplugd: DEVNAME:sda
Jan 16 21:10:59 G530 hotplugd: DEVGUID:0
Jan 16 21:10:59 G530 hotplugd: DEVPATH:sda
Jan 16 21:10:59 G530 hotplugd: SUBSYSTEM:block
Jan 16 21:10:59 G530 hotplugd: PHYSDEVPATH:/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/port-0:0/expander-0:0/port-0:0:0/end_device-0:0:0/target0:0:0/0:0:0:0
Jan 16 21:10:59 G530 synocheckshare: share_delete.c:439 Start to del homes with id 10
Jan 16 21:11:00 G530 synocheckshare: index_index_add_ex.c:125 Indexing daemon is not running
Jan 16 21:11:01 G530 synocheckshare: share_delete.c:439 Start to del photo with id 2
Jan 16 21:11:02 G530 synocheckshare: share_delete.c:439 Start to del surveillance with id 9
Jan 16 21:11:03 G530 hotplugd: hotplugd.c:1358 ==== SATA disk [sda] hotswap [add] ====
Jan 16 21:11:03 G530 hotplugd: enclosure_list_enum.c:93 failed to get enclosure head, please check enclosure firmware/hardware
Jan 16 21:11:03 G530 hotplugd: enclosure_enum_by_valid_link.c:61 Fail to SYNOEnclosureListEnum().
Jan 16 21:11:03 G530 hotplugd: enclosure_serialized_list_get.c:33 failed to enum enclosure lists
Jan 16 21:11:03 G530 hotplugd: enclosure_list_cache_update.c:29 failed to get serialized enclosure list
Jan 16 21:11:03 G530 hotplugd: hotplugd.c:1363 Failed to update enclosure list cache.
Jan 16 21:11:03 G530 hotplugd: disk_is_mv_soc_driver.c:72 Can't get sata chip name from pattern /sys/block/sda/device/../../scsi_host/host*/proc_name
Jan 16 21:11:04 G530 hotplugd: disk/disk_config_single.c:168 apply /usr/syno/bin/DiskApmSet.sh 255 /dev/sda 1>/dev/null 2>&1
Jan 16 21:11:04 G530 hotplugd: disk/disk_config_single.c:168 apply /usr/syno/bin/syno_disk_ctl --wcache-off /dev/sda 1>/dev/null 2>&1
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1383 ==== SATA disk [sda] Model: [WD20EARX-00PASB0 ] ====
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1384 ==== SATA disk [sda] Serial number: [WD-WMAZA7147895] ====
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1385 ==== SATA disk [sda] Firmware version: [51.0AB51] ====
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1274 ##### ACTION:add
Jan 16 21:11:04 G530 hotplugd: DEVNAME:sdb
Jan 16 21:11:04 G530 hotplugd: DEVGUID:0
Jan 16 21:11:04 G530 hotplugd: DEVPATH:sdb
Jan 16 21:11:04 G530 hotplugd: SUBSYSTEM:block
Jan 16 21:11:04 G530 hotplugd: PHYSDEVPATH:/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/port-0:0/expander-0:0/port-0:0:1/end_device-0:0:1/target0:0:1/0:0:1:0
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1358 ==== SATA disk [sdb] hotswap [add] ====
Jan 16 21:11:04 G530 hotplugd: enclosure_list_enum.c:93 failed to get enclosure head, please check enclosure firmware/hardware
Jan 16 21:11:04 G530 hotplugd: enclosure_enum_by_valid_link.c:61 Fail to SYNOEnclosureListEnum().
Jan 16 21:11:04 G530 hotplugd: enclosure_serialized_list_get.c:33 failed to enum enclosure lists
Jan 16 21:11:04 G530 hotplugd: enclosure_list_cache_update.c:29 failed to get serialized enclosure list
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1363 Failed to update enclosure list cache.
Jan 16 21:11:04 G530 hotplugd: disk_is_mv_soc_driver.c:72 Can't get sata chip name from pattern /sys/block/sdb/device/../../scsi_host/host*/proc_name
Jan 16 21:11:04 G530 hotplugd: disk/disk_config_single.c:168 apply /usr/syno/bin/DiskApmSet.sh 255 /dev/sdb 1>/dev/null 2>&1
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1383 ==== SATA disk [sdb] Model: [ST4000DM000-1F2168 ] ====
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1384 ==== SATA disk [sdb] Serial number: [Z3038CR3] ====
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1385 ==== SATA disk [sdb] Firmware version: [CC54] ====
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1274 ##### ACTION:add
Jan 16 21:11:04 G530 hotplugd: DEVNAME:sdc
Jan 16 21:11:04 G530 hotplugd: DEVGUID:0
Jan 16 21:11:04 G530 hotplugd: DEVPATH:sdc
Jan 16 21:11:04 G530 hotplugd: SUBSYSTEM:block
Jan 16 21:11:04 G530 hotplugd: PHYSDEVPATH:/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/port-0:0/expander-0:0/port-0:0:2/end_device-0:0:2/target0:0:2/0:0:2:0
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1358 ==== SATA disk [sdc] hotswap [add] ====
Jan 16 21:11:04 G530 hotplugd: enclosure_list_enum.c:93 failed to get enclosure head, please check enclosure firmware/hardware
Jan 16 21:11:04 G530 hotplugd: enclosure_enum_by_valid_link.c:61 Fail to SYNOEnclosureListEnum().
Jan 16 21:11:04 G530 hotplugd: enclosure_serialized_list_get.c:33 failed to enum enclosure lists
Jan 16 21:11:04 G530 hotplugd: enclosure_list_cache_update.c:29 failed to get serialized enclosure list
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1363 Failed to update enclosure list cache.
Jan 16 21:11:04 G530 hotplugd: disk_is_mv_soc_driver.c:72 Can't get sata chip name from pattern /sys/block/sdc/device/../../scsi_host/host*/proc_name
Jan 16 21:11:04 G530 hotplugd: disk/disk_config_single.c:168 apply /usr/syno/bin/DiskApmSet.sh 255 /dev/sdc 1>/dev/null 2>&1
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1383 ==== SATA disk [sdc] Model: [ST3000DM001-1ER166 ] ====
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1384 ==== SATA disk [sdc] Serial number: [Z500QP6V] ====
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1385 ==== SATA disk [sdc] Firmware version: [CC25] ====
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1274 ##### ACTION:add
Jan 16 21:11:04 G530 hotplugd: DEVNAME:sdd
Jan 16 21:11:04 G530 hotplugd: DEVGUID:0
Jan 16 21:11:04 G530 hotplugd: DEVPATH:sdd
Jan 16 21:11:04 G530 hotplugd: SUBSYSTEM:block
Jan 16 21:11:04 G530 hotplugd: PHYSDEVPATH:/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/port-0:0/expander-0:0/port-0:0:3/end_device-0:0:3/target0:0:3/0:0:3:0
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1358 ==== SATA disk [sdd] hotswap [add] ====
Jan 16 21:11:04 G530 hotplugd: enclosure_list_enum.c:93 failed to get enclosure head, please check enclosure firmware/hardware
Jan 16 21:11:04 G530 hotplugd: enclosure_enum_by_valid_link.c:61 Fail to SYNOEnclosureListEnum().
Jan 16 21:11:04 G530 hotplugd: enclosure_serialized_list_get.c:33 failed to enum enclosure lists
Jan 16 21:11:04 G530 hotplugd: enclosure_list_cache_update.c:29 failed to get serialized enclosure list
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1363 Failed to update enclosure list cache.
Jan 16 21:11:04 G530 hotplugd: disk_is_mv_soc_driver.c:72 Can't get sata chip name from pattern /sys/block/sdd/device/../../scsi_host/host*/proc_name
Jan 16 21:11:04 G530 hotplugd: disk/disk_config_single.c:168 apply /usr/syno/bin/DiskApmSet.sh 255 /dev/sdd 1>/dev/null 2>&1
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1383 ==== SATA disk [sdd] Model: [ST4000DM000-1F2168 ] ====
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1384 ==== SATA disk [sdd] Serial number: [Z303MC89] ====
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1385 ==== SATA disk [sdd] Firmware version: [CC54] ====
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1274 ##### ACTION:add
Jan 16 21:11:04 G530 hotplugd: DEVNAME:sde
Jan 16 21:11:04 G530 hotplugd: DEVGUID:0
Jan 16 21:11:04 G530 hotplugd: DEVPATH:sde
Jan 16 21:11:04 G530 hotplugd: SUBSYSTEM:block
Jan 16 21:11:04 G530 hotplugd: PHYSDEVPATH:/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/port-0:0/expander-0:0/port-0:0:4/end_device-0:0:4/target0:0:4/0:0:4:0
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1358 ==== SATA disk [sde] hotswap [add] ====
Jan 16 21:11:04 G530 hotplugd: enclosure_list_enum.c:93 failed to get enclosure head, please check enclosure firmware/hardware
Jan 16 21:11:04 G530 hotplugd: enclosure_enum_by_valid_link.c:61 Fail to SYNOEnclosureListEnum().
Jan 16 21:11:04 G530 hotplugd: enclosure_serialized_list_get.c:33 failed to enum enclosure lists
Jan 16 21:11:04 G530 hotplugd: enclosure_list_cache_update.c:29 failed to get serialized enclosure list
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1363 Failed to update enclosure list cache.
Jan 16 21:11:04 G530 hotplugd: disk_is_mv_soc_driver.c:72 Can't get sata chip name from pattern /sys/block/sde/device/../../scsi_host/host*/proc_name
Jan 16 21:11:04 G530 hotplugd: disk/disk_config_single.c:168 apply /usr/syno/bin/DiskApmSet.sh 255 /dev/sde 1>/dev/null 2>&1
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1383 ==== SATA disk [sde] Model: [ST3000DM001-1CH166 ] ====
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1384 ==== SATA disk [sde] Serial number: [Z1F3MY6N] ====
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1385 ==== SATA disk [sde] Firmware version: [CC46] ====
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1274 ##### ACTION:add
Jan 16 21:11:04 G530 hotplugd: DEVNAME:sdf
Jan 16 21:11:04 G530 hotplugd: DEVGUID:0
Jan 16 21:11:04 G530 hotplugd: DEVPATH:sdf
Jan 16 21:11:04 G530 hotplugd: SUBSYSTEM:block
Jan 16 21:11:04 G530 hotplugd: PHYSDEVPATH:/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/port-0:0/expander-0:0/port-0:0:5/end_device-0:0:5/target0:0:5/0:0:5:0
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1358 ==== SATA disk [sdf] hotswap [add] ====
Jan 16 21:11:04 G530 hotplugd: enclosure_list_enum.c:93 failed to get enclosure head, please check enclosure firmware/hardware
Jan 16 21:11:04 G530 hotplugd: enclosure_enum_by_valid_link.c:61 Fail to SYNOEnclosureListEnum().
Jan 16 21:11:04 G530 hotplugd: enclosure_serialized_list_get.c:33 failed to enum enclosure lists
Jan 16 21:11:04 G530 hotplugd: enclosure_list_cache_update.c:29 failed to get serialized enclosure list
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1363 Failed to update enclosure list cache.
Jan 16 21:11:04 G530 hotplugd: disk_is_mv_soc_driver.c:72 Can't get sata chip name from pattern /sys/block/sdf/device/../../scsi_host/host*/proc_name
Jan 16 21:11:04 G530 hotplugd: disk/disk_config_single.c:168 apply /usr/syno/bin/DiskApmSet.sh 255 /dev/sdf 1>/dev/null 2>&1
Jan 16 21:11:04 G530 hotplugd: disk/disk_config_single.c:168 apply /usr/syno/bin/syno_disk_ctl --wcache-off /dev/sdf 1>/dev/null 2>&1
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1383 ==== SATA disk [sdf] Model: [WD20EARS-00S8B1 ] ====
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1384 ==== SATA disk [sdf] Serial number: [WD-WCAVY5659881] ====
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1385 ==== SATA disk [sdf] Firmware version: [80.00A80] ====
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1274 ##### ACTION:add
Jan 16 21:11:04 G530 hotplugd: DEVNAME:sdg
Jan 16 21:11:04 G530 hotplugd: DEVGUID:0
Jan 16 21:11:04 G530 hotplugd: DEVPATH:sdg
Jan 16 21:11:04 G530 hotplugd: SUBSYSTEM:block
Jan 16 21:11:04 G530 hotplugd: PHYSDEVPATH:/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/port-0:0/expander-0:0/port-0:0:6/end_device-0:0:6/target0:0:6/0:0:6:0
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1358 ==== SATA disk [sdg] hotswap [add] ====
Jan 16 21:11:04 G530 hotplugd: enclosure_list_enum.c:93 failed to get enclosure head, please check enclosure firmware/hardware
Jan 16 21:11:04 G530 hotplugd: enclosure_enum_by_valid_link.c:61 Fail to SYNOEnclosureListEnum().
Jan 16 21:11:04 G530 hotplugd: enclosure_serialized_list_get.c:33 failed to enum enclosure lists
Jan 16 21:11:04 G530 hotplugd: enclosure_list_cache_update.c:29 failed to get serialized enclosure list
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1363 Failed to update enclosure list cache.
Jan 16 21:11:04 G530 hotplugd: disk_is_mv_soc_driver.c:72 Can't get sata chip name from pattern /sys/block/sdg/device/../../scsi_host/host*/proc_name
Jan 16 21:11:04 G530 hotplugd: disk/disk_config_single.c:168 apply /usr/syno/bin/DiskApmSet.sh 255 /dev/sdg 1>/dev/null 2>&1
Jan 16 21:11:04 G530 hotplugd: disk/disk_config_single.c:168 apply /usr/syno/bin/syno_disk_ctl --wcache-off /dev/sdg 1>/dev/null 2>&1
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1383 ==== SATA disk [sdg] Model: [WD20EARS-00MVWB0 ] ====
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1384 ==== SATA disk [sdg] Serial number: [WD-WMAZA4913001] ====
Jan 16 21:11:04 G530 hotplugd: hotplugd.c:1385 ==== SATA disk [sdg] Firmware version: [51.0AB51] ====
Jan 16 21:11:06 G530 synocheckshare: servicecfg_internal_lib.c:355 skip reload stopping/stopped job [netatalk][0xD300 servicectl_job_reload.c:42]
Jan 16 21:11:06 G530 synocheckshare: service_home_reload.c:91 Failed to reload 'atalk' [0xD300 servicectl_job_reload.c:42]
Jan 16 21:11:06 G530 synocheckshare: synocheckshare.c:74 Failed to enable PGSQL [0x8300]
Jan 16 21:11:08 G530 root: No alive sharebin, pre-start process of php-fpm terminated
Jan 16 21:11:08 G530 [ 61.344332] init: php-fpm pre-start process (22413) terminated with status 1
Jan 16 21:11:09 G530 kernel: [ 62.229083] Get empty minor:105
Jan 16 21:11:12 G530 S99zbootok.sh: all service finish boot up.
Jan 16 21:11:12 G530 synofstool: fs_vol_expansible.c:36 device /dev/vg1000/lv with fs -1 not support resize.[0x0900 fs_type_get_from_disk.c:70]
Jan 16 21:11:12 G530 servicetool: service_third_party.c:38 synoservice: start all packages ...
Jan 16 21:11:12 G530 synopkg: pkgstartstop.cpp:147 Cannot start package [], version
Jan 16 21:11:12 G530 synopkg: pkgstartstop.cpp:147 Cannot start package [], version
Jan 16 21:11:12 G530 synopkg: pkgstartstop.cpp:147 Cannot start package [], version
Jan 16 21:11:12 G530 synopkg: pkgstartstop.cpp:147 Cannot start package [], version
Jan 16 21:11:12 G530 synopkg: pkgstartstop.cpp:147 Cannot start package [], version
Jan 16 21:11:12 G530 synopkg: pkgstartstop.cpp:147 Cannot start package [], version
Jan 16 21:11:12 G530 synopkg: pkgstartstop.cpp:147 Cannot start package [], version
Jan 16 21:11:12 G530 synopkg: pkgstartstop.cpp:147 Cannot start package [], version
Jan 16 21:11:12 G530 servicetool: service_third_party.c:57 synoservice: finish started all packages
Jan 16 21:11:12 G530 root: == DSM finished boot up ==
Jan 16 21:41:19 G530 synomkthumbd: synoidx_ipc_core.cpp:111 [Error] connect server: /tmp/synoindexplugind_sock
Jan 16 21:41:19 G530 synomkthumbd: synomk_ipc.cpp:110 fail
Jan 16 21:41:19 G530 synomkflvd: synoidx_ipc_core.cpp:111 [Error] connect server: /tmp/synoindexplugind_sock
Jan 16 21:41:19 G530 synomkflvd: synomk_ipc.cpp:83 fail
Jan 16 22:14:40 G530 umount: can't umount md0: No such file or directory
[pvdisplay]
Couldn't find device with uuid 'HBo3L0-ZZqp-2ADK-CCSe-3IH8-mmEl-ca6y3Y'.
Couldn't find device with uuid 'HBo3L0-ZZqp-2ADK-CCSe-3IH8-mmEl-ca6y3Y'.
Couldn't find device with uuid 'HBo3L0-ZZqp-2ADK-CCSe-3IH8-mmEl-ca6y3Y'.
Couldn't find device with uuid 'HBo3L0-ZZqp-2ADK-CCSe-3IH8-mmEl-ca6y3Y'.
Couldn't find device with uuid 'HBo3L0-ZZqp-2ADK-CCSe-3IH8-mmEl-ca6y3Y'.
Couldn't find all physical volumes for volume group vg1000.
Couldn't find device with uuid 'HBo3L0-ZZqp-2ADK-CCSe-3IH8-mmEl-ca6y3Y'.
Couldn't find all physical volumes for volume group vg1000.
Couldn't find device with uuid 'HBo3L0-ZZqp-2ADK-CCSe-3IH8-mmEl-ca6y3Y'.
Couldn't find all physical volumes for volume group vg1000.
Couldn't find device with uuid 'HBo3L0-ZZqp-2ADK-CCSe-3IH8-mmEl-ca6y3Y'.
Couldn't find all physical volumes for volume group vg1000.
Volume group "vg1000" not found
Skipping volume group vg1000
Couldn't find device with uuid 'HBo3L0-ZZqp-2ADK-CCSe-3IH8-mmEl-ca6y3Y'.
Couldn't find all physical volumes for volume group vg1000.
Couldn't find device with uuid 'HBo3L0-ZZqp-2ADK-CCSe-3IH8-mmEl-ca6y3Y'.
Couldn't find all physical volumes for volume group vg1000.
Couldn't find device with uuid 'HBo3L0-ZZqp-2ADK-CCSe-3IH8-mmEl-ca6y3Y'.
Couldn't find all physical volumes for volume group vg1000.
Couldn't find device with uuid 'HBo3L0-ZZqp-2ADK-CCSe-3IH8-mmEl-ca6y3Y'.
Couldn't find all physical volumes for volume group vg1000.
Volume group "vg1000" not found
Skipping volume group vg1000
Couldn't find device with uuid 'HBo3L0-ZZqp-2ADK-CCSe-3IH8-mmEl-ca6y3Y'.
Couldn't find all physical volumes for volume group vg1000.
Couldn't find device with uuid 'HBo3L0-ZZqp-2ADK-CCSe-3IH8-mmEl-ca6y3Y'.
Couldn't find all physical volumes for volume group vg1000.
Couldn't find device with uuid 'HBo3L0-ZZqp-2ADK-CCSe-3IH8-mmEl-ca6y3Y'.
Couldn't find all physical volumes for volume group vg1000.
Couldn't find device with uuid 'HBo3L0-ZZqp-2ADK-CCSe-3IH8-mmEl-ca6y3Y'.
Couldn't find all physical volumes for volume group vg1000.
Volume group "vg1000" not found
Skipping volume group vg1000
[/etc/lvm/backup/vg1000]
# Generated by LVM2 version 2.02.38 (2008-06-11): Sat Jan 16 04:00:38 2016
contents = "Text Format Volume Group"
version = 1
description = "Created *after* executing '/sbin/lvextend --alloc inherit /dev/vg1000/lv -l100%VG'"
creation_host = "G530" # Linux G530 3.10.35 #1 SMP Sat Dec 12 17:01:14 MSK 2015 x86_64
creation_time = 1452938438 # Sat Jan 16 04:00:38 2016
vg1000 {
id = "OJ3oNy-SLGN-RvdT-KLiG-jDs2-JbxB-4ommso"
seqno = 14
status = ["RESIZEABLE", "READ", "WRITE"]
extent_size = 8192 # 4 Megabytes
max_lv = 0
max_pv = 0
physical_volumes {
pv0 {
id = "8peoYO-TObT-0aOB-soTA-flZO-rySk-I9DTbB"
device = "/dev/md2" # Hint only
status = ["ALLOCATABLE"]
dev_size = 19486833408 # 9.07426 Terabytes
pe_start = 1152
pe_count = 2378763 # 9.07426 Terabytes
}
pv1 {
id = "HBo3L0-ZZqp-2ADK-CCSe-3IH8-mmEl-ca6y3Y"
device = "/dev/md3" # Hint only
status = ["ALLOCATABLE"]
dev_size = 3906970496 # 1.81932 Terabytes
pe_start = 1152
pe_count = 476925 # 1.81932 Terabytes
}
pv2 {
id = "JgNxgM-8R3t-AO6s-DCRs-pR3x-Fk1z-3dyCXk"
device = "/dev/md4" # Hint only
status = ["ALLOCATABLE"]
dev_size = 1953485824 # 931.495 Gigabytes
pe_start = 1152
pe_count = 238462 # 931.492 Gigabytes
}
}
logical_volumes {
lv {
id = "d8HMle-nC1C-Cx9s-f6ml-d2Lm-mC3R-S1ZjfX"
status = ["READ", "WRITE", "VISIBLE"]
segment_count = 5
segment1 {
start_extent = 0
extent_count = 1427258 # 5.44456 Terabytes
type = "striped"
stripe_count = 1 # linear
stripes = [
"pv0", 0
]
}
segment2 {
start_extent = 1427258
extent_count = 238462 # 931.492 Gigabytes
type = "striped"
stripe_count = 1 # linear
stripes = [
"pv1", 0
]
}
segment3 {
start_extent = 1665720
extent_count = 951505 # 3.6297 Terabytes
type = "striped"
stripe_count = 1 # linear
stripes = [
"pv0", 1427258
]
}
segment4 {
start_extent = 2617225
extent_count = 238463 # 931.496 Gigabytes
type = "striped"
stripe_count = 1 # linear
stripes = [
"pv1", 238462
]
}
segment5 {
start_extent = 2855688
extent_count = 238462 # 931.492 Gigabytes
type = "striped"
stripe_count = 1 # linear
stripes = [
"pv2", 0
]
}
}
}
}
[/etc/lvm/archive/vg1000_* - starting with expansion of last disk]
# vg1000_0012.vg
# Generated by LVM2 version 2.02.38 (2008-06-11): Sat Jan 16 04:00:37 2016
contents = "Text Format Volume Group"
version = 1
description = "Created *before* executing '/sbin/vgextend /dev/vg1000 /dev/md4'"
creation_host = "G530" # Linux G530 3.10.35 #1 SMP Sat Dec 12 17:01:14 MSK 2015 x86_64
creation_time = 1452938437 # Sat Jan 16 04:00:37 2016
vg1000 {
id = "OJ3oNy-SLGN-RvdT-KLiG-jDs2-JbxB-4ommso"
seqno = 12
status = ["RESIZEABLE", "READ", "WRITE"]
extent_size = 8192 # 4 Megabytes
max_lv = 0
max_pv = 0
physical_volumes {
pv0 {
id = "8peoYO-TObT-0aOB-soTA-flZO-rySk-I9DTbB"
device = "/dev/md2" # Hint only
status = ["ALLOCATABLE"]
dev_size = 19486833408 # 9.07426 Terabytes
pe_start = 1152
pe_count = 2378763 # 9.07426 Terabytes
}
pv1 {
id = "HBo3L0-ZZqp-2ADK-CCSe-3IH8-mmEl-ca6y3Y"
device = "/dev/md3" # Hint only
status = ["ALLOCATABLE"]
dev_size = 3906970496 # 1.81932 Terabytes
pe_start = 1152
pe_count = 476925 # 1.81932 Terabytes
}
}
logical_volumes {
lv {
id = "d8HMle-nC1C-Cx9s-f6ml-d2Lm-mC3R-S1ZjfX"
status = ["READ", "WRITE", "VISIBLE"]
segment_count = 4
segment1 {
start_extent = 0
extent_count = 1427258 # 5.44456 Terabytes
type = "striped"
stripe_count = 1 # linear
stripes = [
"pv0", 0
]
}
segment2 {
start_extent = 1427258
extent_count = 238462 # 931.492 Gigabytes
type = "striped"
stripe_count = 1 # linear
stripes = [
"pv1", 0
]
}
segment3 {
start_extent = 1665720
extent_count = 951505 # 3.6297 Terabytes
type = "striped"
stripe_count = 1 # linear
stripes = [
"pv0", 1427258
]
}
segment4 {
start_extent = 2617225
extent_count = 238463 # 931.496 Gigabytes
type = "striped"
stripe_count = 1 # linear
stripes = [
"pv1", 238462
]
}
}
}
}
# vg1000_0013.vg
# Generated by LVM2 version 2.02.38 (2008-06-11): Sat Jan 16 04:00:38 2016
contents = "Text Format Volume Group"
version = 1
description = "Created *before* executing '/sbin/lvextend --alloc inherit /dev/vg1000/lv -l100%VG'"
creation_host = "G530" # Linux G530 3.10.35 #1 SMP Sat Dec 12 17:01:14 MSK 2015 x86_64
creation_time = 1452938438 # Sat Jan 16 04:00:38 2016
vg1000 {
id = "OJ3oNy-SLGN-RvdT-KLiG-jDs2-JbxB-4ommso"
seqno = 13
status = ["RESIZEABLE", "READ", "WRITE"]
extent_size = 8192 # 4 Megabytes
max_lv = 0
max_pv = 0
physical_volumes {
pv0 {
id = "8peoYO-TObT-0aOB-soTA-flZO-rySk-I9DTbB"
device = "/dev/md2" # Hint only
status = ["ALLOCATABLE"]
dev_size = 19486833408 # 9.07426 Terabytes
pe_start = 1152
pe_count = 2378763 # 9.07426 Terabytes
}
pv1 {
id = "HBo3L0-ZZqp-2ADK-CCSe-3IH8-mmEl-ca6y3Y"
device = "/dev/md3" # Hint only
status = ["ALLOCATABLE"]
dev_size = 3906970496 # 1.81932 Terabytes
pe_start = 1152
pe_count = 476925 # 1.81932 Terabytes
}
pv2 {
id = "JgNxgM-8R3t-AO6s-DCRs-pR3x-Fk1z-3dyCXk"
device = "/dev/md4" # Hint only
status = ["ALLOCATABLE"]
dev_size = 1953485824 # 931.495 Gigabytes
pe_start = 1152
pe_count = 238462 # 931.492 Gigabytes
}
}
logical_volumes {
lv {
id = "d8HMle-nC1C-Cx9s-f6ml-d2Lm-mC3R-S1ZjfX"
status = ["READ", "WRITE", "VISIBLE"]
segment_count = 4
segment1 {
start_extent = 0
extent_count = 1427258 # 5.44456 Terabytes
type = "striped"
stripe_count = 1 # linear
stripes = [
"pv0", 0
]
}
segment2 {
start_extent = 1427258
extent_count = 238462 # 931.492 Gigabytes
type = "striped"
stripe_count = 1 # linear
stripes = [
"pv1", 0
]
}
segment3 {
start_extent = 1665720
extent_count = 951505 # 3.6297 Terabytes
type = "striped"
stripe_count = 1 # linear
stripes = [
"pv0", 1427258
]
}
segment4 {
start_extent = 2617225
extent_count = 238463 # 931.496 Gigabytes
type = "striped"
stripe_count = 1 # linear
stripes = [
"pv1", 238462
]
}
}
}
}
^ permalink raw reply
* Re: broken raid level 5 array caused by user error
From: Mathias Mueller @ 2016-01-19 14:35 UTC (permalink / raw)
To: Phil Turmel; +Cc: Linux raid, linux-raid-owner
In-Reply-To: <569D384F.6070208@turmel.org>
Hi Phil,
I forgot to add some information: when I was creating the bytestrings
from my jpg file, I did not start from 0k but from 100k of the jpg file
(to skip the jpg header).
> Very interesting. You could go one step further and compare the jpeg
> file contents in the first 1M against the locations found to determine
> where the chunks actually start and end on each device. The final
> offset will be a chunk multiple before these boundaries. Or do md5
> sums
> of 4k blocks to reduce the amount to inspect.
How exactly can I do this? Should I create more Bytestrings and do more
brep with them on my physical devices? I have already results from
searching bytestrings with an offset of 64k (starting from 100k to 612k
of my jpeg file, so 9 bytestrings at all). Should I provide a table of
the results?
> This will help (and looks correct), but I don't remember what we did to
> try to find the beginning of your filesystem. Did we search for a
> filesystem signature? Please re-summarize that.
Yes, we were searching for an ext4 signature, there were some fragments
of old file systems, but you also found two promising signatures, both
with this timestamp: Sun, 08 Nov 2015 20:06:00 GMT (which is
approximately the last time I mounted the filesystem)
here is a link to the archived message:
http://www.spinics.net/lists/raid/msg50433.html
the device names have changed from the archived post to now:
sdb -> sdf Serial Number: JK1170YBHYV6MD
sdc -> sdc Serial Number: JK1100YAG64A1T
sdd -> sde Serial Number: JK1121YAG7YDLS
sde -> sdd Serial Number: ML0220F30PZUVD
Thanks and best regards
Mathias
^ permalink raw reply
* Re: ICH RAID5 delisted and broken after mdadm installation
From: Пётр Б. @ 2016-01-19 16:13 UTC (permalink / raw)
To: linux-raid
In-Reply-To: <CA+Ni7jM-Ad4G=_23uL9K-4Ya46K2NV-0LqnaaQW7fR4+npMPXA@mail.gmail.com>
Fixed it myself with these tips:
https://communities.intel.com/thread/26252?tstart=0
http://marc.info/?l=linux-raid&m=134308187613187&w=2
Now, for some strange reason it was working for some time and then got
delisted again ("Offline members" in BIOS). Assembled and started with
mdadm and it worked again after reboot.
2016-01-18 20:13 GMT+03:00, Пётр Б. <satnatantas@gmail.com>:
> I found a mistake: sdc contains Windows and is failing, not sdb.
>
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply
* Re: broken raid level 5 array caused by user error
From: Phil Turmel @ 2016-01-19 17:51 UTC (permalink / raw)
To: Mathias Mueller; +Cc: Linux raid, linux-raid-owner
In-Reply-To: <bb6cce6b0d5bb6c653ef94e4a58388cf@pingofdeath.de>
[-- Attachment #1: Type: text/plain, Size: 1389 bytes --]
Hi Mathias,
On 01/19/2016 09:35 AM, Mathias Mueller wrote:
> Hi Phil,
>
> I forgot to add some information: when I was creating the bytestrings
> from my jpg file, I did not start from 0k but from 100k of the jpg file
> (to skip the jpg header).
Ok. But I'm still not confident of chunk boundaries.
>> Very interesting. You could go one step further and compare the jpeg
>> file contents in the first 1M against the locations found to determine
>> where the chunks actually start and end on each device. The final
>> offset will be a chunk multiple before these boundaries. Or do md5 sums
>> of 4k blocks to reduce the amount to inspect.
>
> How exactly can I do this? Should I create more Bytestrings and do more
> brep with them on my physical devices? I have already results from
> searching bytestrings with an offset of 64k (starting from 100k to 612k
> of my jpeg file, so 9 bytestrings at all). Should I provide a table of
> the results?
Sigh. I couldn't help myself. New utility attached. Curse you Mathias
for an interesting problem! ;-)
Call it with your jpeg and the devices to search, like so:
findHash.py /path/to/picture.jpeg /dev/sd[bcde]
It'll make a map of hashes of each 4k block in the jpeg and then search
the listed devices for those hashes, building a map of the file
fragments. This will clearly show chunk boundaries.
Please show the output.
Phil
[-- Attachment #2: findHash.py --]
[-- Type: text/x-python, Size: 2243 bytes --]
#! /usr/bin/python2
#
# Locate 4k fragments of a subject file in one or more other files or
# devices. Only reports two or more consecutive matches.
#
# Usage:
# findHash.py /path/to/subject/file /dev/sdx|/path/to/image/file [/dev/sdy ...]
import hashlib, sys, datetime
# Read the known file 4k at a time, building a dictionary of
# md5 hashes vs. offset. Use a large buffer for speed.
# Drops any partial block at the end of the file.
d = {}
pos = long(0)
f = open(sys.argv[1], 'r', 1<<20)
b = f.read(4096)
while len(b)==4096:
md5 = hashlib.md5()
md5.update(b)
h = md5.digest()
hlist = d.get(h)
if not hlist:
hlist = []
d[h] = hlist
# print "New hash %s at %8.8x" % (h.encode('hex'), pos)
hlist.append(pos)
pos += 4096
b = f.read(4096)
f.close()
print "%d Unique hashes in %s" % (len(d), sys.argv[1])
def checkAndPrint(match):
if match[2]>4096:
print "%20s @ %12.12x:%12.12x ~= %8.8x:%8.8x" % (fname, match[1], match[1]+match[2]-1, match[0], match[0]+match[2]-1)
# Read the candidate files/devices, looking for possible matches. Match
# entries are vectors of known file offset, candidate file offset, and
# length.
for fname in sys.argv[2:]:
print "\nSearching for pieces of %s in %s:..." % (sys.argv[1], fname)
pos = long(0)
f = open(fname, 'r', 1<<24)
matches = []
b = f.read(4096)
lastts = None
while len(b)==4096:
if not (pos & 0x7ffffff):
ts = datetime.datetime.now()
if lastts:
print "@ %12.12x %.1fMB/s \r" % (pos, 128.0/((ts-lastts).total_seconds())),
else:
print "@ %12.12x...\r" % pos,
sys.stdout.flush()
lastts = ts
md5 = hashlib.md5()
md5.update(b)
h = md5.digest()
if h in d:
i = 0
while i<len(matches):
match = matches[i]
target = match[0]+match[2]
continuations = [x for x in d[h] if x==target]
if continuations:
match[2] += 4096
i += 1
else:
del matches[i]
checkAndPrint(match)
if not matches:
matches = [[x, pos, 4096] for x in d[h]]
else:
for match in matches:
checkAndPrint(match)
matches = []
pos += 4096
b = f.read(4096)
print "End of %s at %12.12x" % (fname, pos)
# show matches that continue to the end of the candidate file/device.
for match in matches:
checkAndPrint(match)
^ permalink raw reply
* Re: [PATCH] Abort pending request for RAID10
From: Shaohua Li @ 2016-01-19 18:53 UTC (permalink / raw)
To: Hannes Reinecke; +Cc: Neil Brown, linux-raid
In-Reply-To: <1453193726-4617-1-git-send-email-hare@suse.de>
On Tue, Jan 19, 2016 at 09:55:26AM +0100, Hannes Reinecke wrote:
> RAID10 delays the write until the bitmap has been updated.
> So it really should check if the device is still working
> before sending requests, otherwise it'll happily sending
> I/O to a known faulty device.
Hi,
__make_request already checks the faulty bit. That's possible the disk becomes
faulty after __make_request check though. But faulty bit can be set any time,
for example, after the check with your patch. There is no guarantee pending
writes get canceled immediately after the disk is marked faulty. I'm wondering
what's the real problem.
Thanks,
Shaohua
^ permalink raw reply
* Re: broken raid level 5 array caused by user error
From: Phil Turmel @ 2016-01-19 19:37 UTC (permalink / raw)
To: Mathias Mueller; +Cc: Linux raid, linux-raid-owner
In-Reply-To: <569E77AF.6040906@turmel.org>
On 01/19/2016 12:51 PM, Phil Turmel wrote:
> Sigh. I couldn't help myself. New utility attached. Curse you Mathias
> for an interesting problem! ;-)
I decided that this might be useful to others, particularly if someone
wants to tweak it for more parallelization, so I prettied it up for
github with a readme and a proper copyright statement.
https://github.com/pturmel/findHash
Phil
^ permalink raw reply
* [PATCH] util: fix wrong return value of cluster_get_dlmlock
From: Guoqing Jiang @ 2016-01-20 8:21 UTC (permalink / raw)
To: neilb; +Cc: linux-raid, Guoqing Jiang
Actually lksb.sb_status means that a node get the lock
or not instead of the return value of dlm_lock.
Signed-off-by: Guoqing Jiang <gqjiang@suse.com>
---
util.c | 14 ++++----------
1 file changed, 4 insertions(+), 10 deletions(-)
diff --git a/util.c b/util.c
index f1b0b95..cf9572b 100644
--- a/util.c
+++ b/util.c
@@ -142,7 +142,7 @@ int cluster_get_dlmlock(int *lockid)
dlm_lock_res->ls = dlm_hooks->create_lockspace(cluster_name, O_RDWR);
if (!dlm_lock_res->ls) {
pr_err("%s failed to create lockspace\n", cluster_name);
- goto out;
+ return -ENOMEM;
}
/* Conversions need the lockid in the LKSB */
@@ -157,21 +157,15 @@ int cluster_get_dlmlock(int *lockid)
dlm_lock_res, NULL, NULL);
if (ret) {
pr_err("error %d when get PW mode on lock %s\n", errno, str);
- goto out;
+ dlm_hooks->release_lockspace(cluster_name, dlm_lock_res->ls, 1);
+ return ret;
}
/* Wait for it to complete */
poll_for_ast(dlm_lock_res->ls);
*lockid = dlm_lock_res->lksb.sb_lkid;
- errno = dlm_lock_res->lksb.sb_status;
- if (errno) {
- pr_err("error %d happened in ast with lock %s\n", errno, str);
- goto out;
- }
-
-out:
- return ret;
+ return dlm_lock_res->lksb.sb_status;
}
int cluster_release_dlmlock(int lockid)
--
2.6.2
^ permalink raw reply related
* Re: WANTED new maintainer for Linux/md (and mdadm)
From: Artur Paszkiewicz @ 2016-01-20 8:27 UTC (permalink / raw)
To: NeilBrown, linux-raid, dm-devel, LKML
Cc: Linus Torvalds, J. Bruce Fields, Phil Turmel
In-Reply-To: <87k2o849j5.fsf@notabene.neil.brown.name>
On 12/21/2015 07:10 AM, NeilBrown wrote:
>
> hi,
> I became maintainer for md (Linux Software RAID) in late 2001 and on
> the whole it has been fun and a valuable experience. But I have been
> losing interest in recent years (https://lwn.net/Articles/511073/) and
> as was mentioned at the kernel summit, I would like to resign. Some
> years ago I managed to hand over nfsd to the excellent Bruce Fields,
> but I do not seem to have the gift that Linus has of attracting
> maintainers. While there are a number of people who know quite a bit
> about md and/or have contributed to development, there is no obvious
> candidate for replacement maintainer - no one who has already been
> doing significant parts of the maintainer role.
>
> So I have decided to fall back on the mechanism by which I ended up
> being maintainer in the first place. I will create a vacuum and hope
> someone fills it (yes: I was sucked-in....). So as of 1st February
> 2016 I will be resigning.
>
> At the kernel summit in October Linus talked about the value of
> maintainership teams (https://lwn.net/Articles/662979/). I think it
> would be great if a (small) team formed to continue to oversee md
> rather than just a single individual (or maybe the dm team could extend
> to include md??). If I had managed to be part of a team rather than
> "going it alone" for so long, I might feel less tired of the whole
> thing now.
>
> I don't see it as my place to appoint that team or any individuals, or
> even to nominate any candidates. A very important attribute of a
> maintainer is that they need to care about the code and the subsystem
> and I cannot tell other people to care (or even know if they do). It
> is really up to individuals to volunteer. A few people have been
> mentioned to me in earlier less-public conversations. Any of them may
> well be suitable, but I would rather they named themselves if
> interested.
>
> So I'm hoping to get one or more volunteers to be maintainer:
> - to gather and manage patches and outstanding issues,
> - to review patches or get them reviewed
> - to follow up bug reports and get them resolved
> - to feed patches upstream, maybe directly to Linus,
> maybe through some other maintainer, depending on what
> relationships already exist or can be formed,
> - to guide the longer term direction (saying "no" is important
> sometimes),
> - to care,
> but also to be aware that maintainership takes real effort and time, as
> does anything that is really worthwhile.
>
> This all applies to mdadm as well as md (except you would ultimately
> *be* upstream for mdadm, not needing to send it anywhere). Even if a
> clear team doesn't form it would be great if different people
> maintained mdadm and md.
>
> One part of the job that I have put a lot of time in to is following
> the linux-raid@vger.kernel.org list and providing support. This makes
> people feel good about md and so more adventurous in using it.
> Consequently I tend to hear about bugs and usability issues nice and
> early (well before paying customers hit them in most cases) and that is
> a big win.
> In recent times I've been doing less of this and have been absolutely
> thrilled that the gap has been more than filled by other very competent
> community members. Not developers particular but a number of md users
> have been providing excellent support. I'd particularly like to
> high-light Phil Turmel who is very forthcoming with excellent advice,
> but he is certainly not the only one who deserves a lot of thanks.
> So "Thank you" to everyone who answers questions on linux-raid.
>
> This would be a good place for any future maintainer to hang out to
> receive wisdom as well as to provide support.
>
> I will still be around. I can certainly help out in some sort of
> mentor role, and can probably be convinced to review patches and
> comment on designs. But I really want to head towards spending less
> time on md (there are so many other interesting things to learn about).
>
> So: if anyone is interested - please announce yourself, ask questions
> and start doing things. I have no clear idea about how a transition
> will happen. That is really up to you (plural). Take the bull by the
> horns and start *being* a maintainer(team). I won't get in your way
> and I'll help where I can.
>
> Thanks,
> NeilBrown
>
> P.S. I'm committed to continue to work with the raid5-journal effort
> From Facebook and the raid1-cluster effort from SUSE and the
> line-in-the-sand of 1st February won't affect my support for those.
>
Hi Neil,
Thank you for your work and time spent on maintaining MD/mdadm. I would also
like to offer help for the emerging maintainership team. I've been working with
MD RAID for more than 4 years, mostly testing and developing the IMSM-related
parts on behalf of my employer - Intel. I realize that I was not very visible
on this mailing list, but I think I have a pretty good knowledge about mdadm
and the MD drivers. Now I have Intel's approval to take on maintaining MD RAID
as part of my job, not focusing primarily on IMSM. I definitely feel more
confident with maintaining mdadm, but I would certainly like to learn more
about the kernel MD stack and help with it as much as I can.
Regards,
Artur
^ permalink raw reply
* Re: broken raid level 5 array caused by user error
From: Mathias Mueller @ 2016-01-20 9:04 UTC (permalink / raw)
To: Phil Turmel; +Cc: Linux raid, linux-raid-owner
In-Reply-To: <569E905D.9010606@turmel.org>
Hi Phil,
thanks a lot for your patience and sorry for driving you crazy. I will
post results as soon as your nice tool has finished :)
Mathias
^ permalink raw reply
* Re: Intel IMSM RAID 5 won't start - now jbd2 blocked for more than 120 seconds
From: Guido D'Arezzo @ 2016-01-20 9:48 UTC (permalink / raw)
To: linux-raid
I hope this is of use. After recovering the RAID, the drives were
used heavily, backing up and restoring, A while later, Arch Linux hung
for unknown reasons and after reset (Intel ME reset: as before, the
o/s was unresponsive) the RAID began a resync. I resumed copying etc,
discs busy, and ran 'find / something', which hung. After a while
everything resumed without apparent harm. Here are extracts from
journalctl:
Jan 11 10:20:27 archlinux kernel: Linux version 4.2.5-1-ARCH
(builduser@tobias) (gcc version 5.2.0 (GCC) ) #1 SMP PREEMPT Tue Oct
27 08:13:28 CET 2015
...
Jan 11 10:20:27 archlinux kernel: DMI: VIGLEN DQ77MK/DQ77MK, BIOS
MKQ7710H.86A.0062.2013.0902.1328 09/02/2013
...
Jan 11 10:20:27 archlinux kernel: raid6: sse2x1 gen() 6958 MB/s
Jan 11 10:20:27 archlinux kernel: random: nonblocking pool is initialized
Jan 11 10:20:27 archlinux kernel: raid6: sse2x1 xor() 6766 MB/s
Jan 11 10:20:27 archlinux kernel: raid6: sse2x2 gen() 12676 MB/s
Jan 11 10:20:27 archlinux kernel: raid6: sse2x2 xor() 8365 MB/s
Jan 11 10:20:27 archlinux kernel: raid6: sse2x4 gen() 10430 MB/s
Jan 11 10:20:27 archlinux kernel: raid6: sse2x4 xor() 7014 MB/s
Jan 11 10:20:27 archlinux kernel: raid6: using algorithm sse2x2 gen() 12676 MB/s
Jan 11 10:20:27 archlinux kernel: raid6: .... xor() 8365 MB/s, rmw enabled
Jan 11 10:20:27 archlinux kernel: raid6: using ssse3x2 recovery algorithm
Jan 11 10:20:27 archlinux kernel: async_tx: api initialized (async)
Jan 11 10:20:27 archlinux kernel: xor: automatically using best
checksumming function:
Jan 11 10:20:27 archlinux kernel: avx : 27582.000 MB/sec
Jan 11 10:20:27 archlinux kernel: md: raid6 personality registered for level 6
Jan 11 10:20:27 archlinux kernel: md: raid5 personality registered for level 5
Jan 11 10:20:27 archlinux kernel: md: raid4 personality registered for level 4
Jan 11 10:20:27 archlinux kernel: md/raid:md126: device sdd
operational as raid disk 0
Jan 11 10:20:27 archlinux kernel: md/raid:md126: device sda
operational as raid disk 1
Jan 11 10:20:27 archlinux kernel: md/raid:md126: device sdc
operational as raid disk 2
Jan 11 10:20:27 archlinux kernel: md/raid:md126: device sdb
operational as raid disk 3
Jan 11 10:20:27 archlinux kernel: md/raid:md126: allocated 4366kB
Jan 11 10:20:27 archlinux kernel: md/raid:md126: raid level 5 active
with 4 out of 4 devices, algorithm 0
Jan 11 10:20:27 archlinux kernel: RAID conf printout:
Jan 11 10:20:27 archlinux kernel: --- level:5 rd:4 wd:4
Jan 11 10:20:27 archlinux kernel: disk 0, o:1, dev:sdd
Jan 11 10:20:27 archlinux kernel: disk 1, o:1, dev:sda
Jan 11 10:20:27 archlinux kernel: disk 2, o:1, dev:sdc
Jan 11 10:20:27 archlinux kernel: disk 3, o:1, dev:sdb
Jan 11 10:20:27 archlinux kernel: md126: detected capacity change from
0 to 101494816768
Jan 11 10:20:27 archlinux kernel: md: md126 switched to read-write mode.
Jan 11 10:20:27 archlinux kernel: md: bind<sdb>
Jan 11 10:20:27 archlinux kernel: md: bind<sdc>
Jan 11 10:20:27 archlinux kernel: md: bind<sda>
Jan 11 10:20:27 archlinux kernel: md: bind<sdd>
Jan 11 10:20:27 archlinux kernel: md/raid:md125: not clean -- starting
background reconstruction
Jan 11 10:20:27 archlinux kernel: md/raid:md125: device sdd
operational as raid disk 0
Jan 11 10:20:27 archlinux kernel: md/raid:md125: device sda
operational as raid disk 1
Jan 11 10:20:27 archlinux kernel: md/raid:md125: device sdc
operational as raid disk 2
Jan 11 10:20:27 archlinux kernel: md/raid:md125: device sdb
operational as raid disk 3
Jan 11 10:20:27 archlinux kernel: md/raid:md125: allocated 4366kB
Jan 11 10:20:27 archlinux kernel: md/raid:md125: raid level 5 active
with 4 out of 4 devices, algorithm 0
Jan 11 10:20:27 archlinux kernel: RAID conf printout:
Jan 11 10:20:27 archlinux kernel: --- level:5 rd:4 wd:4
Jan 11 10:20:27 archlinux kernel: disk 0, o:1, dev:sdd
Jan 11 10:20:27 archlinux kernel: disk 1, o:1, dev:sda
Jan 11 10:20:27 archlinux kernel: disk 2, o:1, dev:sdc
Jan 11 10:20:27 archlinux kernel: disk 3, o:1, dev:sdb
Jan 11 10:20:27 archlinux kernel: md125: detected capacity change from
0 to 2899102924800
Jan 11 10:20:27 archlinux kernel: md: md125 switched to read-write mode.
Jan 11 10:20:27 archlinux kernel: md: resync of RAID array md125
Jan 11 10:20:27 archlinux kernel: md: minimum _guaranteed_ speed:
1000 KB/sec/disk.
Jan 11 10:20:27 archlinux kernel: md: using maximum available idle IO
bandwidth (but not more than 200000 KB/sec) for resync.
Jan 11 10:20:27 archlinux kernel: md: using 128k window, over a total
of 943718400k.
Jan 11 10:20:27 archlinux kernel: md: resuming resync of md125 from checkpoint.
Jan 11 10:20:27 archlinux kernel: md125: p1 p2 p3
Jan 11 10:20:27 archlinux kernel: device-mapper: uevent: version 1.0.3
Jan 11 10:20:27 archlinux kernel: device-mapper: ioctl: 4.33.0-ioctl
(2015-8-18) initialised: dm-devel@redhat.com
Jan 11 10:20:27 archlinux kernel: EXT4-fs (dm-2): mounted filesystem
with ordered data mode. Opts: (null)
...
Jan 11 10:20:27 archlinux kernel: EXT4-fs (dm-2): re-mounted. Opts:
stripe=64,data=ordered
...
Jan 11 10:35:17 archlinux systemd[1]: Starting Cleanup of Temporary
Directories...
Jan 11 10:35:18 archlinux systemd[1]: Started Cleanup of Temporary Directories.
...
Jan 11 10:40:13 archlinux kernel: INFO: task jbd2/dm-2-8:325 blocked
for more than 120 seconds.
Jan 11 10:40:13 archlinux kernel: Not tainted 4.2.5-1-ARCH #1
Jan 11 10:40:13 archlinux kernel: "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 11 10:40:13 archlinux kernel: jbd2/dm-2-8 D ffff88042e255200
0 325 2 0x00000000
Jan 11 10:40:13 archlinux kernel: ffff880418d97c78 0000000000000046
ffff88041c279b80 ffff880418943700
Jan 11 10:40:13 archlinux kernel: 0000000000000001 ffff880418d98000
ffff880418d97d70 ffff880418d97d58
Jan 11 10:40:13 archlinux kernel: ffff880418943700 ffff8804182e5400
ffff880418d97c98 ffffffff8157283e
Jan 11 10:40:13 archlinux kernel: Call Trace:
Jan 11 10:40:13 archlinux kernel: [<ffffffff8157283e>] schedule+0x3e/0x90
Jan 11 10:40:13 archlinux kernel: [<ffffffffa02344e1>]
jbd2_journal_commit_transaction+0x231/0x1890 [jbd2]
Jan 11 10:40:13 archlinux kernel: [<ffffffff810a8239>] ?
dequeue_entity+0x149/0x690
Jan 11 10:40:13 archlinux kernel: [<ffffffff810a9071>] ?
put_prev_entity+0x31/0x420
Jan 11 10:40:13 archlinux kernel: [<ffffffff810b4c80>] ?
wake_atomic_t_function+0x60/0x60
Jan 11 10:40:13 archlinux kernel: [<ffffffff810dca8e>] ?
try_to_del_timer_sync+0x5e/0x90
Jan 11 10:40:13 archlinux kernel: [<ffffffffa023ab4a>]
kjournald2+0xca/0x250 [jbd2]
Jan 11 10:40:13 archlinux kernel: [<ffffffff810b4c80>] ?
wake_atomic_t_function+0x60/0x60
Jan 11 10:40:13 archlinux kernel: [<ffffffffa023aa80>] ?
commit_timeout+0x10/0x10 [jbd2]
Jan 11 10:40:13 archlinux kernel: [<ffffffff81092578>] kthread+0xd8/0xf0
Jan 11 10:40:13 archlinux kernel: [<ffffffff810924a0>] ?
kthread_worker_fn+0x170/0x170
Jan 11 10:40:13 archlinux kernel: [<ffffffff8157665f>] ret_from_fork+0x3f/0x70
Jan 11 10:40:13 archlinux kernel: [<ffffffff810924a0>] ?
kthread_worker_fn+0x170/0x170
Jan 11 10:40:13 archlinux kernel: INFO: task find:1536 blocked for
more than 120 seconds.
Jan 11 10:40:13 archlinux kernel: Not tainted 4.2.5-1-ARCH #1
Jan 11 10:40:13 archlinux kernel: "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 11 10:40:13 archlinux kernel: find D 0000000000000001
0 1536 1262 0x00000004
Jan 11 10:40:13 archlinux kernel: ffff8800b726b9e8 0000000000000082
ffff8800b10fe040 ffff8804173244c0
Jan 11 10:40:13 archlinux kernel: ffff8800b726b9d8 ffff8800b726c000
ffff88042e255200 7fffffffffffffff
Jan 11 10:40:13 archlinux kernel: 0000000000000002 ffffffff81573110
ffff8800b726ba08 ffffffff8157283e
Jan 11 10:40:13 archlinux kernel: Call Trace:
Jan 11 10:40:13 archlinux kernel: [<ffffffff81573110>] ? bit_wait+0x50/0x50
Jan 11 10:40:13 archlinux kernel: [<ffffffff8157283e>] schedule+0x3e/0x90
Jan 11 10:40:13 archlinux kernel: [<ffffffff81575205>]
schedule_timeout+0x1b5/0x240
Jan 11 10:40:13 archlinux kernel: [<ffffffff8101e769>] ? read_tsc+0x9/0x10
Jan 11 10:40:13 archlinux kernel: [<ffffffff811115e6>] ?
delayacct_end+0x56/0x60
Jan 11 10:40:13 archlinux kernel: [<ffffffff8101e769>] ? read_tsc+0x9/0x10
Jan 11 10:40:13 archlinux kernel: [<ffffffff81573110>] ? bit_wait+0x50/0x50
Jan 11 10:40:13 archlinux kernel: [<ffffffff81571d94>]
io_schedule_timeout+0xa4/0x110
Jan 11 10:40:13 archlinux kernel: [<ffffffff810b4744>] ?
prepare_to_wait_exclusive+0x54/0x80
Jan 11 10:40:13 archlinux kernel: [<ffffffff81573145>] bit_wait_io+0x35/0x50
Jan 11 10:40:13 archlinux kernel: [<ffffffff81572f2b>]
__wait_on_bit_lock+0x4b/0xa0
Jan 11 10:40:13 archlinux kernel: [<ffffffff81573110>] ? bit_wait+0x50/0x50
Jan 11 10:40:13 archlinux kernel: [<ffffffff81573002>]
out_of_line_wait_on_bit_lock+0x82/0xb0
Jan 11 10:40:13 archlinux kernel: [<ffffffff810b4cc0>] ?
autoremove_wake_function+0x40/0x40
Jan 11 10:40:13 archlinux kernel: [<ffffffff810b4cc0>] ?
autoremove_wake_function+0x40/0x40
Jan 11 10:40:13 archlinux kernel: [<ffffffff81203f67>] __lock_buffer+0x27/0x30
Jan 11 10:40:13 archlinux kernel: [<ffffffffa0232b6c>]
do_get_write_access+0x1ec/0x510 [jbd2]
Jan 11 10:40:13 archlinux kernel: [<ffffffffa024a80f>] ?
ext4_htree_store_dirent+0xdf/0x120 [ext4]
Jan 11 10:40:13 archlinux kernel: [<ffffffff812058ca>] ?
__find_get_block+0xaa/0x110
Jan 11 10:40:13 archlinux kernel: [<ffffffffa0232ec7>]
jbd2_journal_get_write_access+0x37/0x70 [jbd2]
Jan 11 10:40:13 archlinux kernel: [<ffffffffa0283391>]
__ext4_journal_get_write_access+0x31/0x70 [ext4]
Jan 11 10:40:13 archlinux kernel: [<ffffffffa0253de5>]
ext4_reserve_inode_write+0x75/0xa0 [ext4]
Jan 11 10:40:13 archlinux kernel: [<ffffffffa0257388>] ?
ext4_dirty_inode+0x48/0x70 [ext4]
Jan 11 10:40:13 archlinux kernel: [<ffffffffa0253e5e>]
ext4_mark_inode_dirty+0x4e/0x220 [ext4]
Jan 11 10:40:13 archlinux kernel: [<ffffffffa0257388>]
ext4_dirty_inode+0x48/0x70 [ext4]
Jan 11 10:40:13 archlinux kernel: [<ffffffff811fc648>]
__mark_inode_dirty+0x48/0x380
Jan 11 10:40:13 archlinux kernel: [<ffffffff811ea579>]
generic_update_time+0x79/0xc0
Jan 11 10:40:13 archlinux kernel: [<ffffffff811ebde6>] touch_atime+0xa6/0xd0
Jan 11 10:40:13 archlinux kernel: [<ffffffff811e2ebb>] iterate_dir+0xdb/0x120
Jan 11 10:40:13 archlinux kernel: [<ffffffff811e330d>] SyS_getdents+0x8d/0x100
Jan 11 10:40:13 archlinux kernel: [<ffffffff811e2fd0>] ? fillonedir+0xd0/0xd0
Jan 11 10:40:13 archlinux kernel: [<ffffffff8157626e>]
entry_SYSCALL_64_fastpath+0x12/0x71
...
^ permalink raw reply
* [PATCH] raid6/algos.c : bug fix : Add the missing definitions to the pq.h file
From: Gayatri Kammela @ 2016-01-21 22:02 UTC (permalink / raw)
To: linux-raid
Cc: linux-kernel, Gayatri Kammela, NeilBrown, Anton Blanchard,
Fenghua Yu
Adding these pr_info and pr_err definitions so as to allow code to be
compiled successfully for testing in userspace, since the printk has
been replaced by pr_info and pr_err in algos.c
Absence of these definitions result in the compilation errors
such as ' undefined reference to `pr_info' ' ' undefined reference to
`pr_err' '
Cc: NeilBrown <neilb@suse.com>
Cc: Anton Blanchard <anton@samba.org>
Cc: Fenghua Yu <fenghua.yu@intel.com>
Signed-off-by: Gayatri Kammela <gayatri.kammela@intel.com>
---
include/linux/raid/pq.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/linux/raid/pq.h b/include/linux/raid/pq.h
index a7a06d1dcf9c..a0118d5929a9 100644
--- a/include/linux/raid/pq.h
+++ b/include/linux/raid/pq.h
@@ -152,6 +152,8 @@ void raid6_dual_recov(int disks, size_t bytes, int faila, int failb,
# define jiffies raid6_jiffies()
# define printk printf
+# define pr_err(format, ...) fprintf(stderr, format, ## __VA_ARGS__)
+# define pr_info(format, ...) fprintf(stdout, format, ## __VA_ARGS__)
# define GFP_KERNEL 0
# define __get_free_pages(x, y) ((unsigned long)mmap(NULL, PAGE_SIZE << (y), \
PROT_READ|PROT_WRITE, \
--
1.9.1
^ permalink raw reply related
* Re: [PATCH] raid6/algos.c : bug fix : Add the missing definitions to the pq.h file
From: Shaohua Li @ 2016-01-21 23:05 UTC (permalink / raw)
To: Gayatri Kammela
Cc: linux-raid, linux-kernel, NeilBrown, Anton Blanchard, Fenghua Yu
In-Reply-To: <1453413759-16064-1-git-send-email-gayatri.kammela@intel.com>
On Thu, Jan 21, 2016 at 02:02:39PM -0800, Gayatri Kammela wrote:
> Adding these pr_info and pr_err definitions so as to allow code to be
> compiled successfully for testing in userspace, since the printk has
> been replaced by pr_info and pr_err in algos.c
>
> Absence of these definitions result in the compilation errors
> such as ' undefined reference to `pr_info' ' ' undefined reference to
> `pr_err' '
>
> Cc: NeilBrown <neilb@suse.com>
> Cc: Anton Blanchard <anton@samba.org>
> Cc: Fenghua Yu <fenghua.yu@intel.com>
> Signed-off-by: Gayatri Kammela <gayatri.kammela@intel.com>
> ---
> include/linux/raid/pq.h | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/include/linux/raid/pq.h b/include/linux/raid/pq.h
> index a7a06d1dcf9c..a0118d5929a9 100644
> --- a/include/linux/raid/pq.h
> +++ b/include/linux/raid/pq.h
> @@ -152,6 +152,8 @@ void raid6_dual_recov(int disks, size_t bytes, int faila, int failb,
>
> # define jiffies raid6_jiffies()
> # define printk printf
> +# define pr_err(format, ...) fprintf(stderr, format, ## __VA_ARGS__)
> +# define pr_info(format, ...) fprintf(stdout, format, ## __VA_ARGS__)
> # define GFP_KERNEL 0
> # define __get_free_pages(x, y) ((unsigned long)mmap(NULL, PAGE_SIZE << (y), \
> PROT_READ|PROT_WRITE, \
Applied, thanks!
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox