Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Problem mounting mdadm RAID on kernel >=4.16.6
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
divined
Apprentice
Apprentice


Joined: 23 Jul 2004
Posts: 162

PostPosted: Sat Jul 21, 2018 8:24 am    Post subject: Problem mounting mdadm RAID on kernel >=4.16.6 Reply with quote

Hello everybody

I've been experiencing this problem mounting my RAID device on kernel version 4.17.6 and greater. Everything falls back to normal once I boot into the 4.17.4 kernel. Specifically, although I can see my RAID being active when executing

Code:

cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4] [raid0] [raid1] [raid10]
md127 : active (auto-read-only) raid1 sdc1[1] sdb1[0]
      976629760 blocks super 1.2 [2/2] [UU]
      bitmap: 0/8 pages [0KB], 65536KB chunk


the system cannot mount the device.

Code:

mount /dev/md127 /mnt/raid
mount: /mnt/raid: mount(2) system call failed: Structure needs cleaning.


I don't believe the structure needs cleaning since I ran fsck on the RAID and no errors popped up. Could something have changed with the latest kernel revisions or could this be a bug?
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 12613

PostPosted: Sat Jul 21, 2018 4:59 pm    Post subject: Reply with quote

Is the problem fixed in 4.17.7? If not, can you bisect to find the specific patch that breaks this?
Back to top
View user's profile Send private message
divined
Apprentice
Apprentice


Joined: 23 Jul 2004
Posts: 162

PostPosted: Sun Jul 22, 2018 6:32 am    Post subject: Reply with quote

The problem seems to persist even in the 4.17.8 kernel. I wouldn't know what further info would be required in order to further clarify and pinpoint the problem.
Back to top
View user's profile Send private message
Hu
Moderator
Moderator


Joined: 06 Mar 2007
Posts: 12613

PostPosted: Sun Jul 22, 2018 5:22 pm    Post subject: Reply with quote

Upstream developers are more receptive to problem reports if you can identify a specific patch, not just a release, in which the problem first appeared. To do that, you need to test the individual patches that are present in the bad kernels and not present in the good kernels. This is a common task, so Git has a helper to let you find this efficiently: git bisect. Tell it the good and bad kernel commits. It will pick a commit midway between and ask you to test that one. Tell it whether the candidate commit is good or bad. It will pick a commit midway between this new point and the appropriate end point based on your answer. This repeats until you identify a specific commit as bad and its parent as good. At that point, you verify your work and report it upstream.
Back to top
View user's profile Send private message
russK
Guru
Guru


Joined: 27 Jun 2006
Posts: 579

PostPosted: Sun Jul 22, 2018 5:37 pm    Post subject: Reply with quote

Have you tried looking at the RAID with 'mdadm --detail' and the devices with 'mdadm --examine'?
Back to top
View user's profile Send private message
axl
Guru
Guru


Joined: 11 Oct 2002
Posts: 389
Location: Romania

PostPosted: Sun Jul 22, 2018 5:49 pm    Post subject: Reply with quote

the array seems to be in read-only. why? any messages in dmesg about the array? does the old kernel work?
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum