[Bug 1445283] [NEW] cannot mount btrfs subvolume by name - No Such File or Directory
Public bug reported: It is not possible to mount a btrfs subvolume by supplying the name to the subvol= argument. The mount only works by using subvolid="ID" where "ID" is the subvolume ID. If you try to mount using the name, "No such file or directory" is returned. # sudo btrfs subvolume list /home ID 3000 gen 109677 top level 5 path ryan/test # sudo mount -t btrfs -o subvol=test /dev/sda1 testdir mount: No such file or directory # sudo mount -t btrfs -o subvolid=3000 /dev/sda1 testdir < successful mount> Ubuntu version: Description:Linux Mint 17.1 Rebecca Release:17.1 Package version: btrfs-tools: Installed: 3.12-1 Candidate: 3.12-1 Version table: *** 3.12-1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status Expected behavior: Subvolume can be mounted by name Actual behavior: Mounting only works when using the ID ** Affects: btrfs (Ubuntu) Importance: Undecided Status: New ** Tags: btrfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1445283 Title: cannot mount btrfs subvolume by name - No Such File or Directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/btrfs/+bug/1445283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1426782] Re: Boot fails with encyprted BTRFS RAID1 array - open ctree failed
*** This bug is a duplicate of bug 1362884 *** https://bugs.launchpad.net/bugs/1362884 Here is the dmesg output at the time of the error message: [8.515396] BTRFS: device fsid e91f611f-524a-43f5-bde5-8ebb9672f146 devid 2 transid 100593 /dev/dm-0 [8.525319] BTRFS info (device dm-0): enabling auto defrag [8.525322] BTRFS info (device dm-0): disk space caching is enabled [8.526281] BTRFS: failed to read the system array on dm-0 [8.547852] BTRFS: open_ctree failed [ 10.106655] BTRFS: device fsid e91f611f-524a-43f5-bde5-8ebb9672f146 devid 3 transid 100593 /dev/dm-1 [ 10.943981] init: mountall main process (334) terminated with status 2 [ 10.972131] init: plymouth-upstart-bridge main process ended, respawning [ 10.976545] init: plymouth-upstart-bridge main process (1253) terminated with status 1 [ 10.976550] init: plymouth-upstart-bridge main process ended, respawning [ 19.846926] BTRFS info (device dm-1): enabling auto defrag [ 19.846929] BTRFS info (device dm-1): disk space caching is enabled [ 19.901994] BTRFS: bdev /dev/dm-0 errs: wr 0, rd 79, flush 0, corrupt 0, gen 0 [ 23.125160] init: failsafe main process (1465) killed by TERM signal ** This bug has been marked a duplicate of bug 1362884 Only one device of multidevice btrfs is decrypted in cryptroot ** No longer affects: upstart (Ubuntu) ** Also affects: cryptsetup (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1426782 Title: Boot fails with encyprted BTRFS RAID1 array - open ctree failed To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1426782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1426782] Re: Boot fails with encyprted BTRFS RAID1 array - open ctree failed
** Package changed: ubuntu => upstart (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1426782 Title: Boot fails with encyprted BTRFS RAID1 array - open ctree failed To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1426782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1426782] Re: Boot fails with encyprted BTRFS RAID1 array - open ctree failed
Today's update to the 3.13.46-77 kernel did not change the behavior. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1426782 Title: Boot fails with encyprted BTRFS RAID1 array - open ctree failed To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1426782/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1426782] Re: Boot fails with encyprted BTRFS RAID1 array - open ctree failed
OK, the workaround from OpenSUSE did NOT work (with the 3.16 kernel).
Same behavior as before. The steps I performed were:
copy /lib/udev.rules.d/64-btrfs.rules to /etc/udev/64-btrfs.rules
The line
IMPORT{builtin}="btrfs ready $devnode"
was already present in the original rules file, so I did not have to
replace anything as I did in OpenSUSE.
** Description changed:
I have recently installed Linux Mint 17.1 into a system with three
drives - 1 SSD containing the / partition (btrfs format), and 2
identical HDD's containing /home in an encrypted BTRFS RAID1 array. The
system will not boot without manual intervention, using either the
recommended 3.13.0-37 kernel or the most up to date 3.16.0-31 kernel.
At about the same time that I am prompted to enter my password to unlock
the drive, I am prompted that a mount has failed. If I press M to enter
manual recovery I see the emergency shell. Then all I have to do is exit
(Ctrl+D) to continue booting and everything works normally.
It appears that a similar (maybe the same) bug was reported on ArchWiki:
https://wiki.archlinux.org/index.php/Btrfs#BTRFS:_open_ctree_failed
I also experienced this bug on OpenSUSE 13.2 and filed a bug report there:
https://bugzilla.opensuse.org/show_bug.cgi?id=912170
On a possibly related note, I am getting TWO password prompts even
though both encrypted volumes use the same password. On OpenSUSE only
one password was required. My understanding is that as soon as you suppy
one password it is supposed to be tried on each volume in /etc/crypttab.
I will now try the fix that worked for me on OpenSUSE (see bug report)
copy /usr/lib/udev/rules.d/64-btrfs.rules into
/etc/udev/rules.d/64-btrfs.rules and replace the following two lines
ENV{DM_NAME}=="", IMPORT{builtin}="btrfs ready $devnode"
ENV{DM_NAME}=="?*", IMPORT{builtin}="btrfs ready /dev/mapper/$env{DM_NAME}"
with single one
IMPORT{builtin}="btrfs ready $devnode"
and report back what happens.
-
Some system information:
=
relevant excerpts from /etc/fstab:
# SSD containing the main system
# / was on /dev/sda3 during installation
UUID=00a0b482-a861-400f-b29c-b003cbc697f9 / btrfs
defaults,autodefrag,discard,space_cache 0 0
# /boot/efi was on /dev/sda2 during installation
UUID=26CC-DC02 /boot/efi vfatdefaults0 1
# encrypted RAID1 btrfs array containing /home
+ # the btrfs devid's are 2 and 3
UUID=e91f611f-524a-43f5-bde5-8ebb9672f146 /home btrfs
defaults,discard,autodefrag,space_cache 0 0
/etc/crypttab:
encrypted-home-sdb UUID=9c8fb7d0-74e2-4e38-b7c7-6211bbb6d2b1 none luks,
retry=1
encrypted-home-sdc UUID=1ca9d3ba-c409-4127-91f5-e3d9c21242bd none luks,
retry=1
relevant excerpts from dmesg:
[9.487085] BTRFS: device fsid e91f611f-524a-43f5-bde5-8ebb9672f146 devid
3 transid 81360 /dev/dm-0
[9.497773] BTRFS info (device dm-0): turning on discard
[9.497776] BTRFS info (device dm-0): enabling auto defrag
[9.49] BTRFS info (device dm-0): disk space caching is enabled
[9.498565] BTRFS: failed to read the system array on dm-0
[9.522859] BTRFS: open_ctree failed
[ 10.246821] init: mountall main process (322) terminated with status 2
[ 10.275253] init: plymouth-upstart-bridge main process ended, respawning
[ 11.110362] BTRFS info (device dm-0): turning on discard
[ 11.110365] BTRFS info (device dm-0): enabling auto defrag
[ 11.110366] BTRFS info (device dm-0): disk space caching is enabled
[ 11.113918] BTRFS: failed to read the system array on dm-0
[ 11.129428] BTRFS: open_ctree failed
[ 11.714810] BTRFS: device fsid e91f611f-524a-43f5-bde5-8ebb9672f146 devid
2 transid 81360 /dev/dm-1
[ 12.628797] init: mountall main process (1033) terminated with status 2
[ 13.088968] BTRFS info (device dm-1): turning on discard
[ 13.088971] BTRFS info (device dm-1): enabling auto defrag
[ 13.088973] BTRFS info (device dm-1): disk space caching is enabled
[ 13.145755] BTRFS: bdev /dev/mapper/encrypted-home-sdb errs: wr 0, rd 79,
flush 0, corrupt 0, gen 0
[ 16.111916] init: failsafe main process (1436) killed by TERM signal
** Project changed: linuxmint => ubuntu
** Also affects: linuxmint
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1426782
Title:
Boot fails with encyprted BTRFS RAID1 array - open ctree failed
To manage notifications about this bug go to:
https://bugs.launchpad.net/linuxmint/+bug/1426782/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1173761] Re: 14e4:43b1 Broadcom Corporation Device 43b1 (rev 03) - not supported
I can confirm Redstorm's experience. I successfully built the module on kernel 3.8.0.29 (Linux Mint 15 KDE x64). The module loaded right away with modprobe and appears to work on an n network, but it's connecting in b/g mode and the speed has not been higher than 5.5 MBit/s. A Dlink PCIE wifi adapter with 3 antennas can connect under the same conditions at 30-50 MBit/s. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1173761 Title: 14e4:43b1 Broadcom Corporation Device 43b1 (rev 03) - not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1173761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 677783] Re: Redshift does not quit upon logout from session
Confirmed on Fedora x64 with Gnome 3.4. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/677783 Title: Redshift does not quit upon logout from session To manage notifications about this bug go to: https://bugs.launchpad.net/redshift/+bug/677783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 726058] Re: wireless disconnects randomly
This affects me as well. I've tried the 2.6.38 Kernel on an up-to-date Maverick system where wireless normally works fine, on the Natty Beta live disk and a test install of Natty beta. I stay connected but experience about 30% packet loss to my router. I'm using the ath9k driver in 802.11n mode. Atheros AR5008 (rev 01) Please help! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/726058 Title: wireless disconnects randomly -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 649838] Re: Notifications clipped on Intel with xorg-edgers
This bug also affects me. I am running an i5-660 (clarkdale) using the onboard graphics. I use the edgers PPA. Happy to provide any output that might be relevant. -- Notifications clipped on Intel with xorg-edgers https://bugs.launchpad.net/bugs/649838 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 489824] Re: power manager icon on system tray doesn't indicate battery status correctly
Yes, I'm still having this issue on Lucid 64-bit. After booting on battery power the Gnome indicator claims my battery is charged and connected to AC power. I can access the correct charge level by opening the power statistics window, or by plugging and unplugging the AC adapter. My hardware configuration (sudo lshw) is attached. ** Attachment added: "Hardware Configuration.txt" http://launchpadlibrarian.net/50879881/Hardware%20Configuration.txt -- power manager icon on system tray doesn't indicate battery status correctly https://bugs.launchpad.net/bugs/489824 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 555528] Re: Display switching not possible on HP Pavillion dv3510nr notebook [Karmic Regression]
On further investigation, it's possible that this is an ACPI code binding issue. I noticed that when I push FN+F4 (my display switch key) in terminal or a word processor, I get "p" just as if I were typing that key. Maybe it's as simple as reassigning the function key to the appropriate keycode. -- Display switching not possible on HP Pavillion dv3510nr notebook [Karmic Regression] https://bugs.launchpad.net/bugs/28 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 555528] Re: Display switching not possible on HP Pavillion dv3510nr notebook [Karmic Regression]
** Attachment added: "Xorg.0.log" http://launchpadlibrarian.net/43241606/Xorg.0.log -- Display switching not possible on HP Pavillion dv3510nr notebook [Karmic Regression] https://bugs.launchpad.net/bugs/28 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 555528] Re: Display switching not possible on HP Pavillion dv3510nr notebook [Karmic Regression]
** Attachment added: "dmesg output" http://launchpadlibrarian.net/43241548/dmesg%20output.odt -- Display switching not possible on HP Pavillion dv3510nr notebook [Karmic Regression] https://bugs.launchpad.net/bugs/28 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 555528] Re: Display switching not possible on HP Pavillion dv3510nr notebook [Karmic Regression]
** Attachment added: "lspci -vvnn output" http://launchpadlibrarian.net/43241482/lspci%20-vvnn%20output.odt -- Display switching not possible on HP Pavillion dv3510nr notebook [Karmic Regression] https://bugs.launchpad.net/bugs/28 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 544012] Re: Doesn't boot into X if external screen connected to dvi port
I can confirm this bug on Lucid beta 1 x64 with an HP Pavillon dv3510nr laptop using the VGA port. The noveau driver boots beautifully as long as an external is not connected. If it is, boot hangs at the screen that says "ubuntu" and shows five orange dots underneath. I can activate the external monitor after booting using the Monitor Settings tool. I also experienced the problem with the Live CD. -- Doesn't boot into X if external screen connected to dvi port https://bugs.launchpad.net/bugs/544012 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 555528] Re: Display switching not possible on HP Pavillion dv3510nr notebook [Karmic Regression]
** Description changed: Binary package hint: xserver-xorg-video-nouveau When running the noveau driver on an HP Pavillion dv3510nr Notebook (running Lucid Lynx beta 1 x64), it is not possible to switch display modes using the laptop's FN+F4 key. This notebook has an NVIDIA 9300M graphics card. The modes can be changed with the monitor settings application, however. Display switching also does not work using the restricted NVIDIA drivers. In this case, it is possible to control the display mode using the NVIDIA X-server settings application, but any change requires restarting the X server. - Display switching using FN+F4 worked as expected in Karmic and Jaunty + In either case, if I activate the external monitor and turn off the + notebook LCD, then disconnect the external monitor, the LCD does NOT + automatically reactive. This means that I have to manually re-enable + the notebook screen before disconnecting. + + Display switching using FN+F4 worked as expected in Karmic and Jaunty, + and the notebook screen automatically activated when an external monitor + was disconnected. -- Display switching not possible on HP Pavillion dv3510nr notebook [Karmic Regression] https://bugs.launchpad.net/bugs/28 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 555528] Re: Display switching not possible on HP Pavillion dv3510nr notebook [Karmic Regression]
** Description changed: Binary package hint: xserver-xorg-video-nouveau When running the noveau driver on an HP Pavillion dv3510nr Notebook (running Lucid Lynx beta 1 x64), it is not possible to switch display modes using the laptop's FN+F4 key. This notebook has an NVIDIA 9300M - graphics card. - - If booted with an external display, the notebook defaults to "Extend" - mode in which the desktop is spread across both the LCD and the external - monitor, with apparently no way to switch between them. If not booted - with an external monitor, it cannot be activated. + graphics card. The modes can be changed with the monitor settings + application, however. Display switching also does not work using the restricted NVIDIA - drivers. In this case, it is possible to controlwhich displays are - active and in what mode (extend, duplicate, or single) using the NVIDIA - X-server settings application, but any change requires restarting the X - server. + drivers. In this case, it is possible to control the display mode using + the NVIDIA X-server settings application, but any change requires + restarting the X server. Display switching using FN+F4 worked as expected in Karmic and Jaunty -- Display switching not possible on HP Pavillion dv3510nr notebook [Karmic Regression] https://bugs.launchpad.net/bugs/28 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 555531] [NEW] Gnome Indicator Applet displays wrong power status when notebook boots from battery
Public bug reported: When I boot my HP Pavillion dv3510nr notebook on battery power, the battery indicator displayed by Gnome indicates that the computer is plugged in, and the tooltip reads "laptop battery is fully charged." However, if I open up Gnome Power Manager I can see that the battery is discharging and the system is not plugged in. If I then plug the notebook in, the correct battery level will be displayed on the icon and the status will change to "charging." I can then unplug and the battery indicator will behave properly. Lucid beta 1 x64. This bug was also present in Karmic. ** Affects: ubuntu Importance: Undecided Status: New -- Gnome Indicator Applet displays wrong power status when notebook boots from battery https://bugs.launchpad.net/bugs/31 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 555528] [NEW] Display switching not possible on HP Pavillion dv3510nr notebook [Karmic Regression]
Public bug reported: Binary package hint: xserver-xorg-video-nouveau When running the noveau driver on an HP Pavillion dv3510nr Notebook (running Lucid Lynx beta 1 x64), it is not possible to switch display modes using the laptop's FN+F4 key. This notebook has an NVIDIA 9300M graphics card. If booted with an external display, the notebook defaults to "Extend" mode in which the desktop is spread across both the LCD and the external monitor, with apparently no way to switch between them. If not booted with an external monitor, it cannot be activated. Display switching also does not work using the restricted NVIDIA drivers. In this case, it is possible to controlwhich displays are active and in what mode (extend, duplicate, or single) using the NVIDIA X-server settings application, but any change requires restarting the X server. Display switching using FN+F4 worked as expected in Karmic and Jaunty ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New ** Tags: display nvidia regression -- Display switching not possible on HP Pavillion dv3510nr notebook [Karmic Regression] https://bugs.launchpad.net/bugs/28 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 311353] Re: volume control doesn't work with HP laptop volume buttons
hp Pavillon dv3510nr volume up/down keys repeating forever Problem occured on Ubuntu 9.10 and persists in Lucid Beta 1 This temporary fix addressing the lack of a keyup event for these media buttons worked fine for me: http://ubuntuforums.org/showthread.php?t=974723 -- volume control doesn't work with HP laptop volume buttons https://bugs.launchpad.net/bugs/311353 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 491771] Re: [Karmic] battery is charged (when discharging) and unaccurate remaining battery time
I have the same problem running 64-bit Ubuntu Karmic (2.6.31-16 kernel) on an HP dv3510nr notebook. -- [Karmic] battery is charged (when discharging) and unaccurate remaining battery time https://bugs.launchpad.net/bugs/491771 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
