| 2019-05-16 16:05:52 |
DiegoRivera |
bug |
|
|
added bug |
| 2019-05-16 16:30:07 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2019-05-16 16:54:17 |
DiegoRivera |
tags |
|
apport-collected disco |
|
| 2019-05-16 16:54:18 |
DiegoRivera |
description |
Hi!
I've found, quite surprised, that xfsdump doesn't allow dump level numbers outside of the range [0-9]. Given that even storing that number requires a full byte (8 bits), it boggles the mind why more numbers aren't supported. The usefulness of supporting more numbers (24? even 255...) is for taking hourly delta snapshots of live filesystems using xfsdump as a backup measure.
With a simple script one can write a backup that takes a full dump (level 0) of the filesystem for the first backup of a given date, and all other backups during that day are incrementals (levels are > 0 ... i.e. the hour of the day the backup is taken). However, given that the tool only supports [0-9] as the backup level, this seems like an arbitrary limitation.
Is there a real, technical limitation that this level is adhering to?
Cheers! |
Hi!
I've found, quite surprised, that xfsdump doesn't allow dump level numbers outside of the range [0-9]. Given that even storing that number requires a full byte (8 bits), it boggles the mind why more numbers aren't supported. The usefulness of supporting more numbers (24? even 255...) is for taking hourly delta snapshots of live filesystems using xfsdump as a backup measure.
With a simple script one can write a backup that takes a full dump (level 0) of the filesystem for the first backup of a given date, and all other backups during that day are incrementals (levels are > 0 ... i.e. the hour of the day the backup is taken). However, given that the tool only supports [0-9] as the backup level, this seems like an arbitrary limitation.
Is there a real, technical limitation that this level is adhering to?
Cheers!
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: gdm 3277 F.... pulseaudio
diego 3916 F.... pulseaudio
/dev/snd/pcmC0D0p: diego 3916 F...m pulseaudio
/dev/snd/controlC1: gdm 3277 F.... pulseaudio
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2019-04-20 (26 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: ASUS All Series
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=UUID=1e9e8db1-15c8-4369-b27b-1a797cfe8561 ro quiet splash ipv6.disable=1 crashkernel=512M-:192M vt.handoff=1
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
PulseList:
Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.0.0-13-generic N/A
linux-backports-modules-5.0.0-13-generic N/A
linux-firmware 1.178.1
RfKill:
3: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
Tags: disco
Uname: Linux 5.0.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 09/15/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3801
dmi.board.asset.tag: Default string
dmi.board.name: RAMPAGE V EXTREME
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3801:bd09/15/2017:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnRAMPAGEVEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUS |
|
| 2019-05-16 16:54:20 |
DiegoRivera |
attachment added |
|
AlsaInfo.txt https://bugs.launchpad.net/bugs/1829409/+attachment/5264313/+files/AlsaInfo.txt |
|
| 2019-05-16 16:54:21 |
DiegoRivera |
attachment added |
|
CRDA.txt https://bugs.launchpad.net/bugs/1829409/+attachment/5264314/+files/CRDA.txt |
|
| 2019-05-16 16:54:23 |
DiegoRivera |
attachment added |
|
CurrentDmesg.txt https://bugs.launchpad.net/bugs/1829409/+attachment/5264315/+files/CurrentDmesg.txt |
|
| 2019-05-16 16:54:24 |
DiegoRivera |
attachment added |
|
IwConfig.txt https://bugs.launchpad.net/bugs/1829409/+attachment/5264316/+files/IwConfig.txt |
|
| 2019-05-16 16:54:26 |
DiegoRivera |
attachment added |
|
Lspci.txt https://bugs.launchpad.net/bugs/1829409/+attachment/5264317/+files/Lspci.txt |
|
| 2019-05-16 16:54:29 |
DiegoRivera |
attachment added |
|
Lsusb.txt https://bugs.launchpad.net/bugs/1829409/+attachment/5264318/+files/Lsusb.txt |
|
| 2019-05-16 16:54:30 |
DiegoRivera |
attachment added |
|
ProcCpuinfo.txt https://bugs.launchpad.net/bugs/1829409/+attachment/5264319/+files/ProcCpuinfo.txt |
|
| 2019-05-16 16:54:32 |
DiegoRivera |
attachment added |
|
ProcCpuinfoMinimal.txt https://bugs.launchpad.net/bugs/1829409/+attachment/5264320/+files/ProcCpuinfoMinimal.txt |
|
| 2019-05-16 16:54:34 |
DiegoRivera |
attachment added |
|
ProcEnviron.txt https://bugs.launchpad.net/bugs/1829409/+attachment/5264321/+files/ProcEnviron.txt |
|
| 2019-05-16 16:54:36 |
DiegoRivera |
attachment added |
|
ProcInterrupts.txt https://bugs.launchpad.net/bugs/1829409/+attachment/5264322/+files/ProcInterrupts.txt |
|
| 2019-05-16 16:54:37 |
DiegoRivera |
attachment added |
|
ProcModules.txt https://bugs.launchpad.net/bugs/1829409/+attachment/5264323/+files/ProcModules.txt |
|
| 2019-05-16 16:54:40 |
DiegoRivera |
attachment added |
|
UdevDb.txt https://bugs.launchpad.net/bugs/1829409/+attachment/5264324/+files/UdevDb.txt |
|
| 2019-05-16 16:54:43 |
DiegoRivera |
attachment added |
|
WifiSyslog.txt https://bugs.launchpad.net/bugs/1829409/+attachment/5264325/+files/WifiSyslog.txt |
|
| 2019-06-24 03:40:41 |
Kai-Heng Feng |
bug task added |
|
xfsdump (Ubuntu) |
|
