| Summary: | kernel states md0: unknown partition table on version 1.2 arrays | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Marc Krämer <mageia> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | tmb |
| Version: | 5 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | kernel-3.19.8-3.mga5.src.rpm | CVE: | |
| Status comment: | |||
Yeah, it's no problem. The in-kernel raid automount support only handles 0.9 "legacy" metadata, all other metadata formats (1.0, 1.1, 1.2) need mdadm for assembling/managing them, so the above is from kernel informing it's detecting a md device it cant handle. Status:
NEW =>
RESOLVED is there any way to suppress that message, since I use lvm-snapshots for backup, I get these messages quite frequent in the log files. As far as I can tell this happens since kernel 3.19 - the old 3.14 didn't have this log message. |
since update to mageia 5 the kernel states the message md0: unknown partition table Since I've two arrays and only one array states this message, I checked the difference between both. The one which states this message has version 1.2, the other (used for boot-partition) has version 0.9. As the output of "mdadm -D /dev/md0" - looks good, I don't think its severe, but the message is annoying and I'm still a bit worried if everything is really alright. /dev/md0: Version : 1.2 Creation Time : Wed Jul 2 01:06:03 2014 Raid Level : raid1 Array Size : 1932206016 (1842.70 GiB 1978.58 GB) Used Dev Size : 1932206016 (1842.70 GiB 1978.58 GB) Raid Devices : 2 Total Devices : 2 Persistence : Superblock is persistent Update Time : Tue Jul 14 11:32:57 2015 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 Name : h2316062:1 UUID : 98b321db:bd81f644:949e9975:5a25aae8 Events : 1141 Number Major Minor RaidDevice State 0 8 3 0 active sync /dev/sda3 1 8 19 1 active sync /dev/sdb3 Reproducible: Steps to Reproduce: