Just use the parse the date from the snapshot name as Martin mentions.
I'm going to uninstall this plugin as it has made my system unusable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569724
As mentioned in the linked thread, I still don't get why we need to know
when a snapshot was booted last. The only thing I am interested in, was
when it was created. I create my snapshots read-only. So when I want to
_use_ a snapshot more than just booting once, I need to create a rw
subvolume (as
In Bug #833980 Michael Vogt writes:
> I added some code into trunk now that will detect noatime and simply
bail out for now. We need a more clever way of detecting the snapshots
age in this case. The code must ensure that it detects when a snapshot
was booted last, not when it was taken.
Maybe
** Branch linked: lp:~darkdragon-001/apt-btrfs-snapshot/trunk
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569724
Title:
noatime option
To manage notifications about this bug go to:
Hello Michael, I Subscribed you to this issue because you are the
maintainer of the package as stated here:
https://www.ubuntuupdates.org/package/core/groovy/universe/base/apt-
btrfs-snapshot
as @darkdragon-001 stated he created a PR for this that does not rely on
atime but on the filestamp in
Is this getting any attention at all?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569724
Title:
noatime option
To manage notifications about this bug go to:
Please do fix this, this is long overdue :-(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569724
Title:
noatime option
To manage notifications about this bug go to:
I fixed this almost three years ago: https://github.com/darkdragon-001
/apt-btrfs-snapshot/commit/83f6f9d9ca2557b7f0225a7d3fbffd107cd207c4
But merge requests are just ignored: https://code.launchpad.net/apt-
btrfs-snapshot/+activereviews
I am just using my own version since a couple of years:
This bug is still open in Kubuntu 20.04!
A solution for people using SSD (I think today it's the vast majority)
and therefore using "noatime" is still missing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In Bug #833980 Dark Dragon writes: "I think it is better to parse the
snapshot name, since it includes the creation time anyway. Feel free to
review my changes"
Sounds like a good solution to me, but seems to be still not implemented yet.
I'm using Kubuntu 18.10 with a btrfs root partition.
If I
To further illustrate how ridiculous this is, I've updated
/etc/cron.weekly/apt-btrfs-snapshot to make a backup of fstab, remove
all occurrences of noatime, run apt-btrfs-snapshot delete-older-than,
and then move the original fstab back into place.
I understand that there are legitimate concerns
I've stumbled upon the same issue.
Here's what I found:
https://answers.launchpad.net/ubuntu/+source/apt-btrfs-
snapshot/+question/263994
https://bugs.launchpad.net/ubuntu/+source/apt-btrfs-snapshot/+bug/833980
In my opinion "older than" should NOT imply "last accessed/used". Such a
feature
Status changed to 'Confirmed' because the bug affects multiple users.
** 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/1569724
13 matches
Mail list logo
