That is what "-w 90" is for.
-w, --wait, --timeout seconds
Fail if the lock cannot be acquired within seconds.
Besides, the problem as I see it isn't creation of multiple snapshots
per se but the *concurrent* application of multiple snapshots which then
end up nested within
Doesn't flock just create a lock and wait, instead of avoiding multiple
snapshots in the first place?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/852458
Title:
three snapshots created
To manage
@Anybody who can reproduce this
Please change the contents of your file /etc/apt/apt.conf.d/80-btrfs-
snapshot to
DPkg::Pre-Invoke {"if [ -x /usr/bin/apt-btrfs-snapshot ] && apt-btrfs-
snapshot supported; then flock -w 90 -x /run/apt-btrfs-snapshot.lock
apt-btrfs-snapshot snapshot; fi "; };
on
a better workaround is probably to use flock or something like that so
that the invocations don't run at the same time. mount already depends
on util-linux which provides flock, so that checks out for the
dependency question.
--
You received this bug notification because you are a member of
This seems to be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/apt-btrfs-snapshot/+bug/853849
.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/852458
Title:
three snapshots created
To
The problem is that aptdaemon invokes dpkg three times, as mentioned in the
dpkg manual
http://manpages.ubuntu.com/manpages/trusty/man1/dpkg.1.html
Note: front-ends might call dpkg several times per invocation, which might
run the hooks more times than expected.
My very ugly workaround is
I wouldn't tag this bug with a medium priority as in the actual state
apt-btrfs is broken and potentially harmful.
But what's really disturbing here is that while this error was reported
almost a year ago apt-btrfs is still shipped in its current dangerous
state!
I wonder what is
I came here to report the nested snapshot problem also.
It means the affected snapshots must be deleted manually.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/852458
Title:
three snapshots
Hi,
Please see
http://www.ogre.com/node/413
for a work-around.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/852458
Title:
three snapshots created
To manage notifications about this bug go to:
I have witnessed this too. This actually becomes a problem if it is
called more than once in the same second: apt-btrfs-snapshot discards
the microsecond when creating the snapshot name. Since the subvolume
(snapshot) already exists on the second call, btrfs dumps the second
snapshot WITHIN the
I can confirm this:
root@precise-X201:~# btrfs subvolume list -p /
ID 256 parent 5 top level 5 path @
ID 269 parent 5 top level 5 path @apt-snapshot-2012-02-06_10:57:25
ID 270 parent 269 top level 5 path @apt-snapshot-2012-02-06_10:57:25/@
ID 271 parent 5 top level 5 path
** Changed in: apt-btrfs-snapshot (Ubuntu)
Importance: Low = Medium
** Changed in: apt-btrfs-snapshot (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/852458
** Changed in: apt-btrfs-snapshot (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/852458
Title:
three snapshots created
To manage notifications about this bug
Oh, should probably mention this isn't a regression. I've always seen
the issue since I installed the package. Just neglected to actually
report the bug until now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
14 matches
Mail list logo
