Thanks, after loosing 4 terabytes of data due to buggy BTRFS, I moved
away from the file system back to ext4. I still have the machine on a
shelf for the day BTRFS becomes stable or gains recovery tools, so I can
recover and access the data again.
If you want to test this specific case then create
This bug should be reopened. Damiön ran "sudo apt-btrfs-snapshot"
without any subcommand and thus ran into bug 1217828. This was not a
failure to verify if the fix worked or not, it was simply another bug.
Please reopen.
--
You received this bug notification because you are a member of Ubuntu
** Tags removed: verification-needed
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/853849
Title:
Update Fails due to btrfs not being able to take a snapshot
To ma
Sorry forgot to mention the version of the package I tested:
apt-btrfs-snapshot 3.5.1~ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/853849
Title:
Update Fails due to btrfs not being able to
Upgraded a second laptop to 16.04.1
get the exact same message as with 14.04.5
sudo apt-btrfs-snapshot
Traceback (most recent call last):
File "/usr/bin/apt-btrfs-snapshot", line 98, in
if args.command == "supported":
AttributeError: 'Namespace' object has no attribute 'command'
--
Y
On the other laptop:
14.04.5 with proposed enabled
sudo apt-btrfs-snapshot
Traceback (most recent call last):
File "/usr/bin/apt-btrfs-snapshot", line 98, in
if args.command == "supported":
AttributeError: 'Namespace' object has no attribute 'command'
I'll upgrade this machine to 16.04
Ha,ha,ha :D
On the first laptop I now get the message:
"Sorry, your system lacks support for the snapshot feature"
That's one way of solving the bug. :D
I'm upgrading another laptop with the same btrfs config to see what
message I get there.
--
You received this bug notification because you are
The machine from 2011 has been decommissioned but I still have it in
storage. I will try to replicate this bug this weekend using a similar
setup as I see the original FSTAB in this bug-report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
** Changed in: apt-btrfs-snapshot (Ubuntu Xenial)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/853849
Title:
Update Fails due to btrfs not being able to take a sn
Hello Damiön, or anyone else affected,
Accepted apt-btrfs-snapshot into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/apt-btrfs-
snapshot/3.5.1~ubuntu0.2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
This bug was fixed in the package apt-btrfs-snapshot - 3.5.1
---
apt-btrfs-snapshot (3.5.1) yakkety; urgency=medium
* fix mock of "btrfs" binary
-- Michael Vogt Fri, 29 Apr 2016 17:13:19
+0200
** Changed in: apt-btrfs-snapshot (Ubuntu)
Status: Fix Committed => Fix Releas
** Changed in: apt-btrfs-snapshot (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/853849
Title:
Update Fails due to btrfs not being able to take a sn
** Branch linked: lp:~bgeron/apt-btrfs-snapshot/fix-update-fail
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/853849
Title:
Update Fails due to btrfs not being able to take a snapshot
To manage not
You probably need an SSD to reproduce this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/853849
Title:
Update Fails due to btrfs not being able to take a snapshot
To manage notifications about
I'm getting the same error messages on 12.04.2 LTS
ian@ubuntu-pc:~$ lsb_release -rd
Description:Ubuntu 12.04.2 LTS
Release:12.04
ian@ubuntu-pc:~$ sudo apt-btrfs-snapshot supported
[sudo] password for ian:
Supported
Failure using Updater shows this error:
installArchives() faile
** Attachment added: "the directory listing right after taking a snapshot"
https://bugs.launchpad.net/ubuntu/+source/apt-btrfs-snapshot/+bug/853849/+attachment/2536613/+files/ls.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
This is what I get...
x099329@KLMB68684:/tmp$ sudo apt-btrfs-snapshot snapshot --debug
Create a snapshot of '/tmp/apt-btrfs-snapshot-mp-KHC0Hw/@' in
'/tmp/apt-btrfs-snapshot-mp-KHC0Hw/@apt-snapshot---debug2011-10-11_17:38:47'
I've attached the directory listing of /tmp after the snapshot... I
c
Thanks a lot Kat! What happens if you manually create a snapshot with the
folling command:
$ sudo apt-btrfs-snapshot snapshot --debug
any output that may help diagnose the issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
** Changed in: apt-btrfs-snapshot (Ubuntu)
Assignee: (unassigned) => Michael Vogt (mvo)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/853849
Title:
Update Fails due to btrfs not being able to t
This is my fstab (I've modified the UUID's in the post for security) As you can
see the subvolume is @ on /
#
proc/proc procnodev,noexec,nosuid 0 0
# / was on /dev/sda1 during installation
UUID=3a790354-6dcc-4905-afe5- /
Thanks for your bugreport.
The feature requires that there is a subvolume "@" on the root "/". This
is created automatically with the standard patition layout. The check in
apt-btrfs-snapshot needs to improve.
** Changed in: apt-btrfs-snapshot (Ubuntu)
Status: New => Incomplete
** Changed
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
22 matches
Mail list logo
