Your message dated Sun, 27 Aug 2023 23:34:45 +0000
with message-id <[email protected]>
and subject line Re: lxc-create(1) incorrectly says default fstype is ext4
has caused the Debian Bug report #883912,
regarding lxc-create(1) incorrectly says default fstype is ext4
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
883912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883912
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lxc
Version: 1:2.0.7-2
Severity: minor
Dear Maintainer,
man lxc-create says:
> --fstype FSTYPE will create an FSTYPE filesystem on the LV, rather than the
> default, which is ext4.
However, when a container is created with lvm without the --fstype option
it gets an ext3 partition.
In src/lxc/bdev/lxclvm.c, in lvm_create:
> fstype = specs->fstype;
> if (!fstype)
> fstype = DEFAULT_FSTYPE;
In src/lxc/bdev/bdev.h:
> #define DEFAULT_FSTYPE "ext3"
I expected the manual to say the default is ext3, not ext4.
Cheers
-- System Information:
Debian Release: 9.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8),
LANGUAGE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages lxc depends on:
ii init-system-helpers 1.48
ii libapparmor1 2.11.0-3
ii libc6 2.24-11+deb9u1
ii libcap2 1:2.25-1
ii libgnutls30 3.5.8-5+deb9u3
ii liblxc1 1:2.0.7-2
ii libseccomp2 2.3.1-2.1
ii libselinux1 2.6-3+b3
ii lsb-base 9.20161125
ii python3 3.5.3-1
ii python3-lxc 1:2.0.7-2
Versions of packages lxc recommends:
ii bridge-utils 1.5-13+deb9u1
ii debootstrap 1.0.89
ii dirmngr 2.1.18-8~deb9u1
ii dnsmasq-base 2.76-5+deb9u1
ii gnupg 2.1.18-8~deb9u1
ii iptables 1.6.0+snapshot20161117-6
ii libpam-cgfs 2.0.7-1
ii lxcfs 2.0.7-1
ii openssl 1.1.0f-3+deb9u1
ii rsync 3.1.2-1
ii uidmap 1:4.4-4.1
Versions of packages lxc suggests:
pn apparmor <none>
pn btrfs-tools <none>
ii lvm2 2.02.168-2
-- no debconf information
--- End Message ---
--- Begin Message ---
Control: forwarded -1 https://github.com/lxc/lxc/issues/1899
Version: 1:3.0.3-1
This was actually fixed upstream just a short while before the Debian
bug was filed, but they were never linked. The fixed version
corresponds to the first upload of lxc to unstable that would have had
the fix.
Mathias
signature.asc
Description: This is a digitally signed message part
--- End Message ---
