Hi, First of all: I noticed was able to mount my partitions when doing with a different path, which made me investigate my /etc/fstab.
It contained this:
LABEL=data1 /mnt/data btrfs
defaults,noatime,nofail,device=/dev/disk/by-label/data1,device=/dev/disk/by-label/data2
0 0
LABEL=secdata1 /mnt/secdata btrfs
defaults,noatime,nofail,device=/dev/disk/by-label/secdata1,device=/dev/disk/by-label/secdata2
0 0
I now changed it to:
/dev/mapper/data1 /mnt/data btrfs defaults,noatime,nofail 0 0
/dev/mapper/secdata1 /mnt/secdata btrfs defaults,noatime,nofail 0 0
since my initramfs scans for btrfs devices anyways. Looking at
/dev/disk/by-label, only the second disk respectively shows up:
lrwxrwxrwx 1 root root 10 Nov 11 19:32 bootfs -> ../../sde1
lrwxrwxrwx 1 root root 10 Nov 11 19:32 data2 -> ../../dm-3
lrwxrwxrwx 1 root root 10 Nov 11 19:32 secdata2 -> ../../dm-4
However in /dev/mapper, all of them are listed:
lrwxrwxrwx 1 root root 7 Nov 11 19:32 data1 -> ../dm-3
lrwxrwxrwx 1 root root 7 Nov 11 19:32 data2 -> ../dm-1
lrwxrwxrwx 1 root root 7 Nov 11 19:32 rootfs -> ../dm-0
lrwxrwxrwx 1 root root 7 Nov 11 19:32 secdata1 -> ../dm-2
lrwxrwxrwx 1 root root 7 Nov 11 19:32 secdata2 -> ../dm-4
I don't know what's going on there exactly (pointers welcome!) but it
seems the inability to mount is a different issue than the error
messages.
* Robert White <rwh...@pobox.com> [2014-11-11 10:07:25 -0800]:
> Since you just upgraded your kernel I'd check to make sure you have the
> correct chipset and controller card selected. Look at /proc/interrupts and
> see if the controller is sharing an interrupt with some other device that
> could be crossing it up.
I don't really get how to interpret that file I'm afraid. These are
the contents:
CPU0 CPU1
0: 754372 0 IO-APIC-edge timer
8: 0 1 IO-APIC-edge rtc0
9: 0 0 IO-APIC-fasteoi acpi
17: 600 114573 IO-APIC 17-fasteoi ehci_hcd:usb1,
ehci_hcd:usb2, ehci_hcd:usb3
18: 521 1240697 IO-APIC 18-fasteoi ohci_hcd:usb4,
ohci_hcd:usb5, ohci_hcd:usb6, radeon
24: 0 0 PCI-MSI-edge PCIe PME
25: 667 373771 PCI-MSI-edge ahci
26: 408 179898 PCI-MSI-edge eth0
NMI: 31 39 Non-maskable interrupts
LOC: 76628 498768 Local timer interrupts
SPU: 0 0 Spurious interrupts
PMI: 31 39 Performance monitoring interrupts
IWI: 0 2 IRQ work interrupts
RTR: 0 0 APIC ICR read retries
RES: 826089 252701 Rescheduling interrupts
CAL: 270 504 Function call interrupts
TLB: 5704 5023 TLB shootdowns
TRM: 0 0 Thermal event interrupts
THR: 0 0 Threshold APIC interrupts
MCE: 0 0 Machine check exceptions
MCP: 129 129 Machine check polls
THR: 0 0 Hypervisor callback interrupts
ERR: 0
MIS: 0
> Play with your MSI/MSI-X settings (if they are in use try disabling them).
I'll try that if the errors show up again in the next few days - maybe
the reboot actually fixed it after all.
> I'd also actvate SMART and get the smart tools (e.g. "smartmontools" in
> gentoo, so probably something similar for your distro) and check the drive
> health.
I already have a monitoring running which also checks SMART, never had
any problems there. But I'll re-check by hand to be sure.
> So the stack is
> Application ->
> File System ->
> Device Mapper ->
> Encryption ->
> Controller ->
> Wiring ->
> Drive
>
> You are seeing write failures in the controller->wiring->drive section
> somewhere.
Since it started happening after the upgrade, I can still hope it was
just some temporary issue if it doesn't show up again, right? ;)
> Another possible area is if you ever resized the physical partitions but
> didn't properly resize the cryptsetup layer with "cryptsetup resize", but
> that woudl be unlikly to affect multiple drives (unless the mistake was
> symmetric, e.g. you did it to both drives).
This isn't the case.
Thanks!
Florian
--
http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
GPG 0xFD55A072 | http://the-compiler.org/pubkey.asc
I love long mails! | http://email.is-not-s.ms/
pgp3lYWFC5U1w.pgp
Description: PGP signature
