On Mon, Jul 16, 2012 at 10:02:42PM +0200, Helge Kreutzmann wrote:
By chance I saw a slight error in the German output e2fsprogs
programms. I grabed the latest de.po and startet reviewing it;
unfortunately it is quite huge and I only managed to to about 1/3 up
to now.
I found various
Package: multiarch-support
Version: 2.13-33
Forwarding per Russ's observation that multiple required library
packages are depending on multiarch-support, which causes Lintian to
complain.
Given that it is a transitional package, this shouldn't be a big deal,
since it's less than 200k installed
tags 674453 +pending
thanks
Patch applied, thanks.
- Ted
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
tags 674694 +pending
thanks
Patch applied, except that 1 k and 2 k blocksize looks horrible; I
much prefer 1k and 2k blocksize. So I reverted that part of the
patch.
It may be the preferred style for SI units, but these are the same
jokers who suggest the use of ridiculous terms like tibibytes
On Mon, Apr 23, 2012 at 03:22:52PM +0300, Touko Korpela wrote:
Finally, the only file system where someone is likely to be creating
that is this small in this day and age is the /boot filesystem --- and
there, even if the drive using 512-byte emulation, performance isn't
an issue since no
On Mon, Apr 23, 2012 at 06:51:28PM +0300, Touko Korpela wrote:
USB sticks and other flash media are optimised for FAT (using big blocks).
Most of my information comes from LWN article Optimizing Linux with cheap
flash drives https://lwn.net/Articles/428584/
I don't know if linear reads during
On Mon, Apr 23, 2012 at 01:17:34AM +0300, Touko Korpela wrote:
Package: e2fsprogs
Version: 1.42.2-2
Severity: normal
I noticed that mke2fs has a default blocksize of 1024 bytes when it uses
filesystem type 'small' (3-512MB) from mke2fs.conf.
It's a bad thing for performance (more so now
Hi Touko,
Note that bigalloc is still somewhat under development; there are
number of bugs that are still in the kernel code, so at this point I
can't really recommend non-developers use it in production yet...
(Some of the bugs weren't evident at the time of the 1.42 release, or
I would have
On Mon, Apr 02, 2012 at 06:34:39AM +0800, jida...@jidanni.org wrote:
My main motivation is that for years uses see
checking messages at boot.
On a dentist's bill at least checking is separate from treating.
So somehow the user should be more informed about what is going on.
Else he
On Sat, Mar 31, 2012 at 06:39:35AM +0800, jida...@jidanni.org wrote:
Package: util-linux
Version: 2.20.1-4
Severity: wishlist
File: /usr/share/man/man8/fsck.8.gz
X-debbugs-cc: ty...@mit.edu
The man page should say by 'check' we mean that nothing will be altered
on the disk except updating
severity 666725 normal
thanks
On Sun, Apr 01, 2012 at 12:50:58PM +0200, Thomas Arendsen Hein wrote:
When using pwgen -s 1 50 to generate 50 one-char passwords,
only lowercase letters are used.
When using pwgen -s 2 50 to generate 50 two-char passwords,
exactly one lowercase letter and one
One of the reasons why the fsck page is a little vague is that it's a
front end progam which executes a file system specific checker
program. These programs are not necessarily consistent in how they
operate. The way e2fsck, which is the file system checker used for
ext2, ext3, and ext4 (and so
tags 665885 +pending
thanks
On Tue, Mar 27, 2012 at 06:41:42PM +0200, Julien Cristau wrote:
Is this what you are looking for?
% more debian/libcomerr2/DEBIAN/shlibs
libcom_err 2 libcomerr2 (= 1.33-3)
udeb: libcom_err 2 e2fsprogs-udeb (= 1.33-3)
Yep, that looks like what I'd expect.
tags 665427 +pending
thanks
On Fri, Mar 23, 2012 at 10:27:11PM -0400, David Prévot wrote:
We noticed some tiny errors in the mke2fs.conf.5 and tune2fs.8 manpages
while translating them in French (for the manpages-fr-extra package),
please find attach a patch to address these issues.
On Mon, Mar 26, 2012 at 09:53:56PM +0200, Julien Cristau wrote:
Package: e2fsprogs
Version: 1.42.1-2
Severity: important
Tags: d-i
(x-debbugs-cc to debian-boot and the btrfs-tools maintainer)
btrfs-tools-udeb's btrfsctl and mkfs.btrfs seem to be linked against
libcom_err.so.2, and the
On Fri, Mar 09, 2012 at 08:11:05PM +0200, Sami Liedes wrote:
Shrinking a filesystem is currently very CPU intensive. On a 100G ext4
filesystem filled to 50% full by making copies of /usr/share/doc to
$MNTPOINT/doc{1,2,3,...}, running resize2fs on a fairly slow (~5400
rpm) disk and a fast Core
On Mon, Feb 20, 2012 at 09:28:49PM +0100, Simon Ruderich wrote:
dpkg-buildflags /dev/null
Dash, which is (now) the default shell for scripts on Debian,
doesn't support that - and it's used by the buildds I think. I
guess you have bash as your /bin/sh which accepts that syntax.
The
On Mon, Feb 20, 2012 at 09:28:49PM +0100, Simon Ruderich wrote:
On Sun, Feb 19, 2012 at 10:39:40PM -0500, Ted Ts'o wrote:
I don't understand, but it looks like the hardening flags are being
passed, but either (a) they are't correct, or (b) they seemingly have
no effect. Can you help me
On Sun, Feb 19, 2012 at 04:39:38PM +0100, Simon Ruderich wrote:
Dear Maintainer,
It looks like the hardening flags weren't applied in 1.42.1-1.
For example:
$ hardening-check /sbin/fsck.ext4
/sbin/fsck.ext4:
Position Independent Executable: no, normal executable!
tags 654457 +pending
thanks
Thanks for sending a proposed patch! I had to slightly modify it so
it deals with the case where we are building on an ancient distro that
doesn't yet have dpkg-buildflags (since I support building this on
systems such as Ubuntu 10.04 LTS and Debian stable).
I've
On Mon, Jan 02, 2012 at 02:13:02PM +, Ben Hutchings wrote:
Currently the value reported for max_batch_time is really the
value of min_batch_time.
Reported-by: Russell Coker russ...@coker.com.au
Signed-off-by: Ben Hutchings b...@decadent.org.uk
Applied, thanks.
On Tue, Jan 03, 2012 at 11:54:46AM -0600, Eric Sandeen wrote:
I just investigated on this FTBFS issue.
The problem is that extundelete doesn't compile against e2fslibs-dev
versions =1.42. Therefore extundelete was just removed from
Debian/testing, so if this bug can't be resolved
On Wed, Dec 21, 2011 at 02:32:58PM +0100, Goswin von Brederlow wrote:
If we want to improve fsck time then the best thing to do would be
to consider a different default value for the -i option of mke2fs.
This advice is not applicable for ext4, since it will not read unused
portions of the
On Sun, Nov 27, 2011 at 10:27:48PM -0500, Ted Ts'o wrote:
Additionally, the call to msync() is made conditional on HAVE_MSYNC
instead of MS_SYNC by a test in configure.in for that function. On
GNU/Hurd msync() is only a stub, so with this test a potential run-time
error is avoided.
Wait
On Mon, Nov 28, 2011 at 07:37:53PM +0100, Svante Signell wrote:
Checking for HAVE_MSYNC helps because configure finds the stub and
decides it is not usable, see below.
Um, how does configure find the stub if you're just doing an
AC_CHECK_FUNCS(... msync ...)
That just checks if a function
tags 649689 +pending -patch
thanks
On Wed, Nov 23, 2011 at 09:44:34AM +0100, Svante Signell wrote:
The attached patch fixes the FTBFS problems for GNU/Hurd due to the lack
of a PATH_MAX definition. Instead of fixed length strings dynamic
allocation is used.
I fixed this problem a different
On Wed, Nov 16, 2011 at 10:24:23AM +0600, Roman Mamedov wrote:
Hello,
I have just tried the version from Squeeze (1.41.12-4stable1), and it does
work properly
Yes, that's not surprising. The 1.41 version doesn't try to use the
new-style resize2fs ioctl. The fundamental issue is what error
On Wed, Nov 16, 2011 at 02:29:37AM +0600, Roman Mamedov wrote:
reopen 644989 !
thanks
Hello,
With e2fsprogs 1.42~WIP-2011-10-16-1 and
Linux hoshi 3.1.0-libre-lemote-rm2-mfgpt #2 Fri Nov 11 03:07:23 YEKT 2011
mips64 GNU/Linux
Are you using a 32-bit or 64-bit userspace with this
On Mon, Oct 31, 2011 at 12:16:35AM +0100, Laurent Grawet wrote:
Then I would like to know whether chattr +e on files and dirs when
coming from ext3 is enough to trigger online defragmentation in order to
migrate those files to extent format ?
The chattr +e will migrate older files to use the
tag 647245 +pending
thanks
On Tue, Nov 01, 2011 at 01:23:09AM +0100, Samuel Thibault wrote:
Samuel Thibault, le Tue 01 Nov 2011 01:16:58 +0100, a écrit :
Package: e2fsprogs
Version: 1.42~WIP-2011-10-16-1
Severity: important
Actually that might even warrant a serious severity, as
tags 644792 +pending
thanks
On Sun, Oct 09, 2011 at 02:26:20AM -0400, Chris Lawrence wrote:
filefrag seems to get stuck (if -v is not specified) repeatedly
calling the FS_IOC_FIEMAP ioctl in the do..while loop.
I suspect this may have to do with the fix for #631498. It looks like
the
retitle 644425 undefined symbol in /sbin/e2fsck caused by missing dependency
priority 644584 important
merge 644425 644584
thanks
On Fri, Oct 07, 2011 at 03:28:32PM +0800, Yafan Zhao wrote:
Package: e2fsprogs
Version: 1.42~WIP-2011-10-05-1
Severity: grave
Justification: renders package
tags 644502 +pending
thanks
On Thu, Oct 06, 2011 at 02:37:41PM +0200, Svante Signell wrote:
The patch inlined below fixes the remaining FTBFS problems for
GNU/Hurd.
It probably fixes the build problems for GNU/kFreeBSD too. The QIF_*
stuff is only used for quota_v2 and kfree seems to
On Wed, Oct 05, 2011 at 08:59:38PM +0200, Maarten De Munck wrote:
Package: e2fsprogs
Version: 1.42~WIP-2011-10-05-1
Severity: important
fsck.ext4 fails with error: fsck.ext4: symbol lookup error: fsck.ext4:
undefined symbol: set_com_err_gettext. Since this happens on the root
fsck at boot,
On Sun, Oct 02, 2011 at 11:48:44PM -0400, Daniel Kahn Gillmor wrote:
Any chance the resize2fs was a 32-bit binary by any chance?
yes, indeed. this is a ppc64 kernel and a 32-bit powerpc everything-else.
Stupid question. Can you tell me what the sizeof(unsigned long) is on
ppc64 and
On Mon, Oct 03, 2011 at 12:46:52PM -0400, Daniel Kahn Gillmor wrote:
On Mon, 3 Oct 2011 12:04:19 -0400, Ted Ts'o ty...@mit.edu wrote:
Stupid question. Can you tell me what the sizeof(unsigned long) is on
ppc64 and ppc32? I think that might be the problem...
0 abc@tut:~/src/test$ gcc -o
On Mon, Oct 03, 2011 at 01:34:57PM -0400, Daniel Kahn Gillmor wrote:
Does this bug need to be reassigned to the kernel or is it in
e2fsprogs? Do you have a patch you want me to try? (it'd be much
easier for me to try a patched e2fsprogs than a patched kernel on
remote hardware)
Actually
On Sun, Oct 02, 2011 at 05:00:51PM -0400, Daniel Kahn Gillmor wrote:
Performing an on-line resize of /dev/mapper/vg_tut0-usr to 1572864 (4k)
blocks.
resize2fs: Invalid argument While trying to add group #38
1 tut:~#
let me know if there is more information i can provide.
Could you check
On Sun, Oct 02, 2011 at 10:30:47PM -0400, Daniel Kahn Gillmor wrote:
On 10/02/2011 09:41 PM, Theodore Tso wrote:
Oh interesting…. I'm not sure whether this is a kernel bug or a resize2fs
bug.
What version of the kernel are you using? And what architecture? x86_64?
i386?
This
reassign 546388 util-linux
thanks
Sigh, one more time, with feeling
The blkid library is now the responsibility of the util-linux package.
I *think* this issue is already addressed in the revmaped version of
blkid found in util-linux, but I'm not 100% sure, so I'm reassigning it
to the
tags 634883 +pending
thanks
On Wed, Jul 20, 2011 at 09:23:51PM +0200, Helge Kreutzmann wrote:
The man page explains the various options and several times says if
enabled (e.g. for enable_periodic_fsck). From the shipped file I
assume that enabled means a numeric 1 and disabled a numeric 0?
tag 631498 +pending
thanks
On Fri, Jun 24, 2011 at 04:02:23PM +0400, Ibragimov Rinat wrote:
When filefrag uses FIEMAP ioctl its logic differs for ordinary and verbose
(-v) modes. ext4 returns extent on every 32768 block so on large files it is
possible that `filefrag large-file' tells
Hi, since you are the last translator for the German e2fsprogs.pot
file, I'm forwarding this to you. Note that there will be a new
e2fsprogs.pot published soon, for the upcoming e2fsprogs 1.42 release.
If you could include this fix in the next de.po update for e2fsprogs,
I would greatly
Hi, since you're the last translator for the French translation file
for e2fsprogs.pot, I'm forwarding this to you. Note that there will
shortly be a new e2fsprogs.pot file published for the upcoming 1.42
release.
If you could consider this bug report and fix translation if
appropriate in the
tags 627535 +pending
thanks
On Sat, May 21, 2011 at 09:23:42PM +0300, Sami Liedes wrote:
Package: e2fsprogs
Version: 1.41.12-4
Severity: normal
e2fsprogs fails to build if DEB_BUILD_OPTIONS contains nostrip
Thanks for reporting this. I've fixed it in my sources and it will be
in the next
tag 642193 +pending
thanks
On Tue, Sep 20, 2011 at 01:33:38AM -0400, A. Costa wrote:
Found a typo in '/usr/share/man/man8/e2fsck.8.gz', see attached '.diff'.
Thanks for reporting this! I've fixed it in my sources and it will be
in the next release.
-
retitle 614082 e2fsck dies with an OOM on bad triple-indirect block in a dir
inode
thanks
On Sat, Feb 19, 2011 at 06:09:38PM +0300, George Shuklin wrote:
Error storing directory block information (inode=169246423, block=0,
num=3966024): Memory allocation failed
Apologies for not looking at
tag 629883 +pending
thanks
I recently was able to reproduce this. It looks like some shellutil
program used by configure has a 4k line length problem. The problem
doesn't show up on Ubuntu 10.04/x86_64, and it doesn't show up in my
sid/i386 chroot (which is what I normally upload to the ftp
On Thu, Jun 30, 2011 at 09:17:58AM +0100, Steve Langasek wrote:
Please find attached a patch to e2fsprogs to transition it to use of the
multiarch library paths as described at
http://wiki.debian.org/Multiarch/Implementation. This patch has been
applied and is being used successfully in
Hi Steve,
On Thu, Jun 30, 2011 at 09:17:58AM +0100, Steve Langasek wrote:
Please find attached a patch to e2fsprogs to transition it to use of the
multiarch library paths as described at
http://wiki.debian.org/Multiarch/Implementation. This patch has been
applied and is being used
On Fri, Sep 16, 2011 at 05:42:26PM +, Thorsten Glaser wrote:
Source: e2fsprogs
Version: 1.42~WIP-2011-09-16-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
e2fsprogs stopped building with the latest upload.
Relevant build log excerpt:
On Fri, Sep 16, 2011 at 07:47:46PM +, Thorsten Glaser wrote:
Not really, I read it “somewhere”, while trying to familiarise
myself with buildds, but didn’t bookmark this specially (as it
matches what I think is right), see
http://lists.debian.org/debian-68k/2011/09/msg00035.html
Is there
tags 636418 +pending
thanks
On Wed, Aug 03, 2011 at 12:07:29AM +0100, Mark Wooding wrote:
Package: e2fslibs
Version: 1.42~WIP-2011-07-02-1
Severity: important
With this version of e2fslibs, dump 0.4b44-1 is a total loss: it fails
with SIGFPE during pass IV.
Thanks for reporting this! I
On Thu, Sep 15, 2011 at 04:07:07AM +0200, Israel G. Lugo wrote:
There's an off-by-one bug in lib/e2p/mntopts.c:e2p_string2mntopt(), both
in the Debian 1.41.12 version, and the current upstream 1.41.14
version. It's failing to properly recognize any MNTOPT_* options, which
means I can't for
fixed 629883 e2fsprogs/1.41.12-4stable1
thanks
On Thu, Jun 09, 2011 at 10:20:22AM +0200, Didier Raboud wrote:
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
CC /«BUILDDIR»/e2fsprogs-1.41.12/lib/ss/parse.c
My basic impression is that the use of data=journalled can help
reduce the risk (slightly) of serious corruption to some kinds of
databases when the application does not provide appropriate syncs
or journalling on its own (IE: such as text-based Wiki database files).
Yes, although if the
On Mon, Jun 27, 2011 at 05:30:11PM +0200, Lukas Czerner wrote:
I've found some. So although data=journal users are minority, there are
some. That being said I agree with you we should do something about it
- either state that we want to fully support data=journal - and then we
should
On Thu, Jun 23, 2011 at 01:32:48PM -0500, Moffett, Kyle D wrote:
Ted, since this new iteration has no customer data, passwords, keys, or
any other private data, I'm going to try to get approval to release an
exact EC2 image of this system for you to test with, including the fake
data volume
On Sat, Jun 18, 2011 at 11:38:07AM +0200, Philipp Kern wrote:
To the normal ftp-master queue with stable as its distribution target in the
.changes (i.e. the changelog dist bit). But proposed-updates works equally
well.
OK, uploaded. Please let me know if there were any issues/problems.
I
On Sat, Jun 18, 2011 at 12:36:01AM +0200, Philipp Kern wrote:
We cannot use the unstable version verbatim for technical reasons. So I'd
like
to ask you to add a changelog entry with Upload to proposed-updates. and a
version like 1.41.12-4+squeeze1. It needs to be built in a stable chroot
tags 612522 +pending
thanks
On Wed, Feb 09, 2011 at 02:34:36PM -0500, Ted Ts'o wrote:
I've forwarded your suggestions to the maintainer of the French
language e2fsprogs.pot at the Translation Project. Thanks!!
The maintainer of the French language translation file has updated
fr.po per your
On Tue, Apr 05, 2011 at 10:30:11AM -0500, Moffett, Kyle D wrote:
Couple of questions which might give me some clues:
(a) was this a natively formatted ext4 file system, or a ext3 file
system which was later converted to ext4?
All the filesystems were formatted like this using
On Mon, Apr 04, 2011 at 09:24:28AM -0500, Moffett, Kyle D wrote:
Unfortunately it was not a trivial process to install Debian
squeeze onto an EC2 instance; it took a couple ugly Perl scripts,
a patched Debian-Installer, and several manual
post-install-but-before-reboot steps (like fixing up
Hi Kyle,
Sorry for not following up sooner. Are you still able to reproduce
this failure? If I set up an identical Debian stable instance on
EC-2, am I likely to reproduce it myself? Do you have a package list
or EC2 base image I can use as a starting point?
Thanks,
On Sun, Feb 27, 2011 at 04:52:46PM +0100, Christoph Anton Mitterer wrote:
Package: e2fsprogs
Version: 1.41.12-2
Severity: wishlist
AFAIU this is not yet done:
It would be nice, if mke2fs could provide an auto-detect mode or
something like this for setting sitrde and stripe-with.
On Tue, Feb 22, 2011 at 10:15:23PM +0530, Ritesh Raj Sarraf wrote:
Package: e2fsprogs
Version: 1.41.12-2
Severity: normal
I think I have started seeing this message very recently (maybe with the
2.6.37 kernel).
[ 307.168035] EXT4-fs (dm-0): error count: 9
[ 307.168046] EXT4-fs (dm-0):
On Wed, Feb 16, 2011 at 11:17:58PM +0100, Johannes Rohr wrote:
Package: e2fsprogs
Version: 1.41.12-2
Severity: normal
I have run a full read-write surface scan on an ext4 partition on an
external USB hard drive (e2fsck -ccfy /dev/sdb6), which lasted for
about 20 hours. After that, e2fsck
forwarded 612522
thanks
I've forwarded your suggestions to the maintainer of the French
language e2fsprogs.pot at the Translation Project. Thanks!!
Thanks for taking the time in making these corrections available.
- Ted
--
To UNSUBSCRIBE, email
On Mon, Oct 04, 2010 at 03:38:01PM +0200, Mike Hommey wrote:
Package: e2fsprogs
Version: 1.41.12-2
Severity: normal
File: /usr/sbin/filefrag
Filefrag never reports the same perfection, on top of the value being
entirely wrong:
# filefrag /mnt/gnome.raw
/mnt/gnome.raw: 3569 extents
On Mon, Nov 29, 2010 at 02:16:02PM +0100, Raphael Hertzog wrote:
It means we don't need to keep it in RAM since we're not going to
read/modifiy it again in the near future. Thus the writeback can be
started right now since delaying it will not save us anything.
At least that's the way I
On Mon, Nov 29, 2010 at 02:58:16PM +, Ian Jackson wrote:
This is the standard way that ordinary files for which reliability was
important have been updated on Unix for decades. fsync is for files
which need synchronisation with things external to the computer (or at
least, external to
On Mon, Nov 29, 2010 at 09:21:44AM -0600, Jonathan Nieder wrote:
That explanation helps a lot. Thanks, both. (Guillem, I like your
patch very much then. Most files being unpacked in a dpkg run aren't
going to be read back again soon. Perhaps some other kernels will
also interpret it as a
I did some experimenting, and I figured out what was going on. You're
right, (c) doesn't quite work, because delayed allocation meant that
the writeout didn't take place until the fsync() for each file
happened. I didn't see this at first; my apologies.
However, this *does* work:
On Fri, Nov 26, 2010 at 03:53:27PM +0100, Raphael Hertzog wrote:
Just to sum up what dpkg --unpack does in 1.15.8.6:
1/ set the package status as half-installed/reinst-required
2/ extract all the new files as *.dpkg-new
3/ for all the unpacked files: fsync(foo.dpkg-new) followed by
On Fri, Jul 30, 2010 at 10:06:55PM -0400, Ted Ts'o wrote:
On Mon, May 31, 2010 at 08:39:38PM +0200, Toni Mueller wrote:
the -p option is not properly documented. Imho, every option deserves
a top-level entry in a man page, and all other options seem to have it.
I didn't check too
On Sat, Jul 31, 2010 at 08:05:24PM +0200, Jan Schulz wrote:
Package: e2fsprogs
Version: 1.41.12-2
Severity: minor
File: /usr/share/man/man5/e2fsck.conf.5.gz
This will be fixed in the 1.41.13 version of e2fsck. Thanks for
pointing it out.
- Ted
--
On Wed, Nov 17, 2010 at 12:19:14AM -0800, J.P. Larocque wrote:
Hi Ted and Micah,
I ran into the problem in e2fsck that prints:
WARNING: PROGRAMMING BUG IN E2FSCK!
OR SOME BONEHEAD (YOU) IS CHECKING A MOUNTED (LIVE) FILESYSTEM.
inode_link_info[X] is Y, inode.i_links_count is Z.
On Tue, Nov 23, 2010 at 08:33:36AM +, Peter Pearse wrote:
The patch below enables the package to cross build using xdeb
---
+-DEPSTATIC_LIBBLKID = @DEPSTATIC_LIBBLKID@ $(STATIC_LIBUUID)
++# Why add the non static string here?
++# - causes the cross build to fail
++# DEPSTATIC_LIBBLKID =
On Tue, Sep 28, 2010 at 03:24:51PM +0300, Dmitry Baryshev wrote:
Hi.
$ fsck /dev/sdb5
fsck from util-linux-ng 2.17.2
e2fsck 1.41.12 (17-May-2010)
fsck.ext3: Group descriptors look bad... trying backup blocks...
/dev/sdb5: clean, 11/1310720 files, 123484/5242338 blocks
$ fsck -f
On Tue, Sep 28, 2010 at 12:02:01AM +0300, Krasu wrote:
Package: e2fsprogs
Version: 1.41.12-2
Severity: important
I'm getting Resize inode not valid all the time during boot. It fails to
check the root filesystem, which is ext3, and shows a prompt to ebter root
password or continue.
On Sun, Sep 26, 2010 at 03:02:18PM +0400, SIO wrote:
Yes, looks like you are right. I've done that test, and e2fsck
returned 0. Will look into init scripts then
Do you have a preference as to whether I reassign bug #59632 to
initscripts, or we should close it and you can reopen another bug with
tags 594004 +pending
thanks
On Mon, Aug 23, 2010 at 01:09:46AM +0100, Ben Hutchings wrote:
Package: e2fsprogs
Version: 1.41.12-2
Severity: important
resize2fs(8) says:
Optionally, the size parameter may be suffixed by one of the
following the units designators: 's', 'K', 'M', or 'G',
On Sun, Sep 26, 2010 at 01:45:02AM +0100, Ben Hutchings wrote:
Priority *important*?!?
[...]
Because of the potential for data loss in case of confusion.
Umm, how? If the size specified is bigger than the device size,
resize2fs will stop and warn the user.
tag 587531 +pending
thanks
I've checked the following patch into the e2fsprogs source tree, which
will be in 1.41.13.
- Ted
commit 8718359b4057bf2b998f4ac6125e33f20efe60cb
Author: Theodore Ts'o ty...@mit.edu
Date: Sat Sep 25 21:14:06 2010 -0400
On Thu, Aug 19, 2010 at 09:11:39PM +0400, SIO wrote:
Here is my /etc/e2fsck.conf:
[options]
allow_cancellation = true
Though cancellation is allowed, when I hit ^c during check of my root
partition
at system boot, it is remounted as read-only. File system is not flagged as
tag +580236 pending
thanks
On Tue, May 04, 2010 at 06:47:06PM +0200, Michael Schmitt wrote:
as specifying the device with its label does work too. A short sentence about
that could be added too.
This will be fixed in the next release of e2fsprogs.
Regards,
On Sun, Sep 26, 2010 at 02:35:14AM +0100, Ben Hutchings wrote:
But if you're shrinking, you have to resize the filesystem and then the
partition. And the partitioning tool is not so likely to know the size
of the filesystem.
And what partitioning tool uses marketing gigabytes as opposed to
On Mon, May 31, 2010 at 08:39:38PM +0200, Toni Mueller wrote:
the -p option is not properly documented. Imho, every option deserves
a top-level entry in a man page, and all other options seem to have it.
I didn't check too thorougly, though.
The -p option to *which* command in e2fsprogs?
tags 589345 +pending
thanks
On Fri, Jul 16, 2010 at 08:54:49PM +0100, Francis Russell wrote:
Package: e2fsprogs
Version: 1.41.12-2
Severity: minor
The resize2fs manpage says As of this writing, the Linux 2.6 kernel supports
on-line resize for filesystems
mounted using ext3 only. I
tags 588726 +pending
thanks
On Sun, Jul 11, 2010 at 05:36:47PM +0200, Nicolas Boulenguez wrote:
Package: e2fsprogs
Version: 1.41.12-2
Severity: minor
Tags: patch
Here is a trivial patch for this cosmetic change.
Thanks for pointing this out. It will be fixed in the next release of
90 matches
Mail list logo
