Hi, some more information about the issue:
Happens on Sid i386 for me. /boot is a separate partition and / is a btrfs upon a dm_crypt partition. Axel Beckert wrote: > > check_mounted(): Could not open /run/rootdev > > Could not check mount status: No such device or address > > fsck died with exit status 250 I provoked this situation again and also tried Dmitrijs's patch from http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=45;filename=fix-up-fsck.patch;att=1;bug=701776 in combination with Daniel's new wrapper, but that doesn't change anything. /run/rootdev exists in that situation and looks like this: brw------- 1 root root 0, 16 Mar 1 00:56 /run/rootdev It's not mounted at that point. (The root partition is mounted "ro" at /dev/mapper/sda2_crypt in my case.) >From utils.c: 812 fd = open(file, O_RDONLY); 813 if (fd < 0) { 814 fprintf (stderr, "check_mounted(): Could not open %s\n", file); 815 return -errno; 816 } >From open(3): ENXIO The named file is a character special or block special file, and the device associated with this special file does not exist. So "btrfs check" tries to read /run/rootdev but can't find the according device to that block special file. Potential explanations for this behaviour: * /run/rootdev has the wrong major and minor numbers. (But it worked before, e.g. with btrfs-tools from testing. Nevertheless other tools like "less -f" provoke the same error.) * "btrfs check" accesses the blockdevice in a different way than btrfsck did. (But I couldn't find any relevant difference in the source code compared to the code of the working version on a first a glance.) So both explanations seem unrealistic for some reasons... Which suggests that the culprit is probably somewhere else. :-/ Regards, Axel -- ,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `- | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
