On Feb 23, 2012, at 6:48 PM, Sami Liedes wrote:
Package: e2fsprogs
Version: 1.42.1-1
Severity: normal
When investigating why e2resizing a 100G filesystem to 75G takes
several hours of *CPU* time on a Core i7 computer (in the Scanning
inode table phase -- you might get a bug report about
On Feb 23, 2012, at 7:40 PM, Sami Liedes wrote:
tags 661071 patch
thanks
On Fri, Feb 24, 2012 at 01:48:54AM +0200, Sami Liedes wrote:
20 dpkg-source: info: building e2fsprogs in e2fsprogs_1.42.1-1.dsc
21 debian/rules build
priority 647039 normal
thanks
On Oct 29, 2011, at 12:54 PM, Laurent Grawet wrote:
Package: e2fsprogs
Version: 1.42~WIP-2011-10-16-1
Severity: important
Hi,
e4defrag does not work with LVM device nodes. See RHEL Bug 707209.
https://bugzilla.redhat.com/show_bug.cgi?id=707209
Note:
On Oct 2, 2011, at 8:51 PM, Daniel Kahn Gillmor wrote:
Oct 2 16:43:39 tut kernel: [ 168.613177] EXT3-fs (dm-2): warning:
verify_group_input: Last group not full
Oct 2 16:43:39 tut kernel: [ 168.613200] ioctl32(resize2fs:2469):
Unknown cmd fd(4) cmd(80286608){t:'f';sz:40} arg(ffcfc210)
On Apr 3, 2011, at 12:23 AM, Elliott Mitchell wrote:
#326647 needs an argument for `fsck` that is passed to the back-ends that
inhibits precautionary checks. A script is better suited for checking
whether the system is on battery (it could be on a UPS battery instead of
an internal
On Feb 17, 2011, at 3:02 AM, Johannes Rohr wrote:
On Mi, Feb 16, 2011 at 05:47:45 -0500, Ted Ts'o wrote:
debugfs /dev/sdb6
debugfs: icheck 33600 33637
[...]
debugfs: stat 12345
1.41.12 (17-May-2010)
debugfs: icheck 33600 33637
Block Inode number
33600 7
33637 7
debugfs: stat
On Jun 18, 2010, at 3:12 AM, Buehl, Reiner wrote:
Hi Jan,
I tried for a while with alternate hardware and the original controller but
the error did never happen again. I think your idea of a bug in e2fsck's
handling of multiply claimed blocks is the only explanation: Maybe during a
On Jun 18, 2010, at 7:09 AM, Theodore Tso wrote:
It could be an e2fsck bug, or it could be a hardware issue. In my
experience, every time
I've tried digging into problems with e2fsck -fy not fixing all problems in a
single
pass, it's been a hardware problem. That being said, multiply
On Jun 3, 2010, at 8:53 PM, beat.n...@stagecoach-wireless.com wrote:
there appears to be a package version mis-match.
squeeze/ testing: e2fs(libs, progs) are version 2.17.xx
and mount and util-linux are version 2.16.2-0.
If you grab the e2fs(libs, progs) packages version 2.16.2-0 from
On Sun, Nov 15, 2009 at 10:34:33PM +0100, Eugeniy Meshcheryakov wrote:
Hello,
Thanks for reply. This option will probably fix problem with systems
with clock set to local timezone, but not for systems like FreeRunner
where clock content is lost when battery is removed. It will be good to
On Sun, Nov 15, 2009 at 11:02:30PM +0100, Eugeniy Meshcheryakov wrote:
As far as the FreeRunner is concerned, it currently takes me under 8
seconds to check a 70gig SSD drive. If you put 8GB SD card into the
FreeRunner smartphone, the first check after a failed battery should
take at most
On Wed, Oct 28, 2009 at 11:50:54AM +0100, Lucas Nussbaum wrote:
Source: e2fsprogs
Version: 1.41.9-1
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20091028 qa-ftbfs
Justification: FTBFS on amd64
During a rebuild of all packages in sid, your package failed to build
On Sat, Nov 14, 2009 at 02:32:54AM +0100, Eugeniy Meshcheryakov wrote:
13 листопада 2009 о 19:43 -0500 Theodore Tso написав(-ла):
(1) I'm the maintainer. (2) The bug doesn't even vaguely fit the
definition of grave:
makes the package in question unusable or mostly so, or causes
Hi Micah,
Do you have the full e2fsck transcript (it looks like what you
submitted to BTS was only a partial transcript)?
Also, can you tell me something about the files which got the
PROGRAMMING BUG error? It would be useful to see the pathname and
inode breakdown of the inode(s) in question.
severity #549861 normal
thanks
(1) I'm the maintainer. (2) The bug doesn't even vaguely fit the
definition of grave:
makes the package in question unusable or mostly so, or causes
data loss, or introduces a security hole allowing access to the
accounts of users who use the package
You
On Fri, Oct 30, 2009 at 12:29:03AM +0100, Michael Prokop wrote:
As a developer and maintainer of a Debian based live system (mainly
for sysadmins and therefore often used for rescue tasks) I'm
wondering what users without (full) control over the systems they
are investigating are supposed to
On Sun, Oct 25, 2009 at 07:37:43AM +0100, Sven Joachim wrote:
On 2009-10-24 21:06 +0200, Theodore Tso wrote:
diff --git a/debian/control.in b/debian/control.in
index 5d5142c..842d5d0 100644
--- a/debian/control.in
+++ b/debian/control.in
@@ -228,7 +228,11 @@ Description: ext2/ext3
On Thu, Oct 29, 2009 at 02:03:31PM +, Thorsten Glaser wrote:
considering Message #64, why is localtime used by ext2fs anyway?
With all times in UTC (or rather in whatever time_t is) this kind
of problems certainly couln't happen at all?
Ext2fs doesn't use localtime. The problem is some
tags 551795 +pending
thanks
On Tue, Oct 20, 2009 at 08:32:32PM +0200, Sven Joachim wrote:
Package: e2fsprogs
Version: 1.41.9-1
Severity: serious
Recently, the /sbin/fsck binary has moved from e2fsprogs to util-linux.
While this is certainly correct in itself, e2fsprogs needs to
On Fri, Oct 02, 2009 at 11:41:07AM +0200, Alessandro Polverini wrote:
Package: e2fsprogs
Version: 1.41.9-1
Severity: important
I recently upgraded one of my clusters to latest version of e2fsprogs and it
stopped working.
After digging around the logs I discovered that it was because the
On Thu, Sep 24, 2009 at 12:25:00PM +0200, Marc Haber wrote:
I'm in UTC+2; since there is a time difference of approximately two
hours (modulo a few seconds -- it certainly took me more than five
seconds to find the power cord and boot the system again), I guess that
makes it clear that
clone 546388 -1
reassign -1 libblkid1
severity 546388 wishlist
thanks
On Sun, Sep 13, 2009 at 12:49:21AM +0200, Christoph Biedl wrote:
Package: e2fsprogs
Version: 1.41.9-1
Severity: normal
Hello,
appearently blkid cannot deal very well with somewhat special
characters in filesystem
tags 509529 +pending
thanks
On Tue, Dec 23, 2008 at 12:06:19AM +, Matt Zimmerman wrote:
Package: e2fsprogs
Version: 1.41.3-1
Severity: minor
On an armel system with 32M of RAM and no swap, attempting e2fsck on a certain
filesystem (details below) resulted in:
m...@stuff:~$ sudo
On Fri, Aug 14, 2009 at 07:02:28PM -0400, Theodore Tso wrote:
On Fri, Aug 07, 2009 at 05:19:38PM +0200, Christoph Hellwig wrote:
Package: e2fsprogs
Version: 1.41.3-1
Severity: normal
It seems like the filefrag doesn't report the correct results for files
without any allocted blocks
On Fri, Aug 07, 2009 at 05:19:38PM +0200, Christoph Hellwig wrote:
Package: e2fsprogs
Version: 1.41.3-1
Severity: normal
It seems like the filefrag doesn't report the correct results for files
without any allocted blocks...
A whole series of bug fixes for filefrag went into e2fsprogs just
On Sat, Aug 08, 2009 at 02:28:56PM +0200, Wouter Verhelst wrote:
That was my first thought. However, I consider this unlikely, given:
- The problem did not happen when I was running the system off of ext3
rather than ext4 (at least, I do not remember that to be the case).
Well, the last
The following patch will be in the next release of e2fsprogs. If
you'd like to apply it and rebuild it, it will provide the proof you
need that either your laptop RTC clock is bad or there's something
strange going on with the system time on your laptop.
On Thu, Aug 06, 2009 at 10:23:55AM +0200, Wouter Verhelst wrote:
Package: e2fsprogs
Version: 1.41.8-2
Severity: normal
File: /sbin/e2fsck
Due to an incorrect assumption about user interface by the manufacturer,
my laptop has its 'power almost out' LED hidden somewhere to the left,
where
On Wed, Aug 05, 2009 at 10:00:21PM +0200, Christoph Anton Mitterer wrote:
Package: e2fsprogs
Version: 1.41.8-2
Severity: normal
It seems that a typo slipped into /etc/mke2fs.conf:
ext4 and ext4dev use both extents but the manpage and tune2fs says
extent (singular).
Creating a filesystem
On Wed, Jul 29, 2009 at 06:30:36AM +0200, Michael Biebl wrote:
Package: libblkid1
Version: 2.16-2
Severity: serious
Justification: wrong dependencies
Hi,
libblkdi1 has a generated dependency on libuuid1 1.40.3-1.
When I compile hal 0.5.13 against libblkid-dev in a minimal chroot,
On Wed, Jul 29, 2009 at 09:11:30PM +0200, Michael Biebl wrote:
Theodore Tso wrote:
Scott, LaMont, could you subscribe to this bug, and handle it, please?
As Michael pointed out in a subsequent e-mail to this bug, it's a
failure in the shlibs file. The libblkid 1.x packages do not provide
On Sat, Jul 25, 2009 at 05:42:01PM +0200, Marco d'Itri wrote:
Thank you for your testing. It make me suspect that the file name do
not really contain space, but the string '\x20' instead. This is then
interpreted differently by different programs. fsck understand it to
mean 'x20', while
On Sun, Jul 26, 2009 at 10:59:15AM +0930, Arthur Marsh wrote:
For the Debian bug to be closed, perhaps the manual page for fstab(5)
should be changed from:
Well, there still is the issue of fsck and mount potentially handling
backslash-style quoting differently in various different fields;
On Wed, Jul 22, 2009 at 01:55:58PM -0400, Sam Hartman wrote:
package: tzc
severity: grave
version: 2.6.15-5
Hi. tzc depends on libzephyr3 which is no longer present in unstable.
This is blocking the zephyr transition, which is blocking the removal
of libkrb53 from testing.
I plan to
On Thu, Jul 02, 2009 at 08:14:29PM +0200, Goswin von Brederlow wrote:
OK, I see what's going on. We're freeing the mountpoint information
so when we print it in an error message, the error message is getting
printed as garbage.
This probably doesn't qualify as a severity important level
On Thu, Jul 02, 2009 at 12:03:10PM +0200, Goswin Brederlow wrote:
Package: e2fsprogs
Version: 1.41.7-1
Severity: important
File: /sbin/resize2fs
Hi,
when I try to resize a filesystem I get:
% resize2fs -p /dev/s/unseen
resize2fs 1.41.7 (29-June-2009)
Filesystem at
severity 535452 normal
tags 535452 +pending
thanks
OK, I see what's going on. We're freeing the mountpoint information
so when we print it in an error message, the error message is getting
printed as garbage.
This probably doesn't qualify as a severity important level bug (a
bug which has a
tags 531385 +pending
thanks
Thanks for notifying me of this typo in the chattr man page. I have
committed a fix into e2fsprogs's source tree, and it will be in the
next release.
- Ted
--
To UNSUBSCRIBE, email to
On Fri, May 29, 2009 at 12:03:46PM +0200, Metzen, Manfred wrote:
Meanwhile i think it is an problem with a specific mainboard or bios (ECS
P4vxad and Award Bios) and Debian 5.
In the following i do the test always 50 times.
When i put the RAID in a system with ECS P4vxad, Award Bios and
On Sat, Apr 18, 2009 at 01:29:02PM -0400, Theodore Tso wrote:
On Sat, Apr 18, 2009 at 06:20:43PM +0200, Robert Millan wrote:
Attached. Btw, I forgot to mention how did I create the file. This time I
reproduced it with a dd if=/dev/zero of=tmp bs=32k count=1 file.
That will blow up
On Tue, Mar 24, 2009 at 04:20:31PM +0100, Metzen, Manfred wrote:
Package: e2fsprogs
Version: 1.41.3-1
After updating some fileserver from debian 4 (etch) to debian 5
(lenny)(new installation) i have a lot of trouble with
ext3-filesystems on raidarrays. Rebooting often ends in manually
tags 516820 +pending
thanks
I found the problem; the following patch should fix things, and I have
this checked into the e2fsprogs SCM.
- Ted
commit 606638906a0229323d1b2871fdb0d45ea0e7ff62
Author: Theodore Ts'o ty...@mit.edu
Date: Thu May 28
On Fri, May 08, 2009 at 08:39:53PM -0400, Andres Salomon wrote:
Package: e2fsprogs
Version: 1.41.3-1
If I attempt to shrink an ext3 filesystem while mounted (even if
read-only) via resize2fs /dev/hda1 8G, it refuses with:
Filesystem at /dev/hda1 is mounted on /; on-line resizing required
On Sat, May 09, 2009 at 06:22:00PM -0400, Andres Salomon wrote:
Creating a zero-length /etc/mtab file doesn't work if, for some
reason, /etc is mounted read-only. Having a fully supported and
supportable system isn't always available. If resize2fs is going to
stipulate that the filesystem
On Fri, May 01, 2009 at 08:16:01PM +0200, matthieu castet wrote:
Package: e2fsprogs
Version: 1.41.5-1
Severity: normal
File: /sbin/fsck.ext3
recent version cause a storm of i_file_acl_hi should be zero on a old ext3
partion that I mount readonly.
After some investigation it seems
On Sun, Apr 19, 2009 at 09:59:55PM +0200, Wouter Verhelst wrote:
I tried, but those patches do not cleanly apply to the version in
Debian. I presume there's a git repository somewhere that I can clone?
I'll happily try compiling and running that one, if necessary.
There's a git repository
On Sat, Apr 18, 2009 at 06:20:43PM +0200, Robert Millan wrote:
Attached. Btw, I forgot to mention how did I create the file. This time I
reproduced it with a dd if=/dev/zero of=tmp bs=32k count=1 file.
That will blow up instantly with:
tmp: Not enough space to build proposed filesystem
On Sat, Apr 18, 2009 at 09:05:19AM +0200, Wouter Verhelst wrote:
Package: e2fsprogs
Version: 1.41.3-1
Severity: normal
When running resize2fs on an offline filesystem, after calling e2fsck -f
on the filesystem, it now consistently reports 'No space left on
device'. Freeing up space before
tags 516428 +unreproducible
thanks
On Sat, Feb 21, 2009 at 01:20:09PM +0100, Robert Millan wrote:
Package: e2fsprogs
Version: 1.41.3-1
Severity: normal
$ /sbin/mke2fs -j tmp
mke2fs 1.41.3 (12-Oct-2008)
tmp is not a block special device.
Proceed anyway? (y,n) y
$
This used to work
tags 521602 +pending
thanks
On Sat, Mar 28, 2009 at 10:13:36PM +0100, Samuel Thibault wrote:
e2fsprogs currently FTBFS on hurd-i386 because of unconditional use of
the PATH_MAX limit which hurd-i386 doesn't have. The attached patch
just exactly allocates what is required.
Your patch didn't
tags 517015 +pending
thanks
On Tue, Feb 24, 2009 at 08:48:35PM -0800, Mike Bird wrote:
Package: e2fsprogs
Version: 1.41.3-1
Severity: minor
tune2fs -m -1 /dev/foo should be an error.
Thanks for reporting this bug. I've committed a fix for this in the
git repository.
Hm, I wish you could have grabbed the output of dumpe2fs on the
parition before you ran the old e2fsck. That would have been very
helpful indeed.
The change in question is this one:
commit 009c02baf90a55b4b2d9c9e3d0a4cfc3e2531640
Author: Theodore Ts'o ty...@mit.edu
Date: Thu Jul 10 16:35:05
tags 511207 +pending
thanks
On Thu, Jan 08, 2009 at 02:21:18PM +, Colin Watson wrote:
Package: e2fsprogs-udeb
Version: 1.41.3-1
Severity: wishlist
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu ubuntu-patch jaunty
In order to support ext4 in d-i (which I'm
On Sun, Dec 28, 2008 at 04:33:28PM +0100, Christoph Thomas wrote:
Package: e2fsprogs
Version: 1.41.3-1
Followup-For: Bug #509893
EXT4-fs: dm-5: Filesystem with huge files cannot be mounted read-write
without CONFIG_LSF.
Is there a particular reason why you are choosing to build your
On Sat, Dec 27, 2008 at 03:51:30PM +0100, Christoph Thomas wrote:
Package: e2fsprogs
Version: 1.41.3-1
Severity: normal
Tags: patch
Hello,
due to an error in the confiuration /etc/mke2fs.conf it is not
possible to mount an ext4 /ext4dev fs after creation.
Line 12 / 16 use the unknown
On Tue, Dec 02, 2008 at 02:45:17PM +0200, Eric Pozharski wrote:
Package: e2fsprogs
Version: 1.088-1
Severity: normal
Accidental build against stable Blibexception-class-perl (1.21-1)
discovered that BPerl::Critic prerequires BException::Class
explicitly. It needs 1.23 at least. Buildlog
tags 503057 +pending
thanks
Thanks for bug report and for the patch to fix things. I've committed
it into the e2fsprogs source tree for updating.
I'm guessing this blows up the ability to make initrd's on x86_64
systems, so it would be worthwhile to apply for an freeze exception
for this
On Tue, Oct 21, 2008 at 08:15:10AM -0200, Rogério Brito wrote:
On Oct 20 2008, Alexandre Lymberopoulos wrote:
It's not a memory stick, it's a hard disk with ext3 file system. I
just plugged it it and the disk was automatically mounted in /dev/ext3
with no abnormal messages in dmesg.
Ok,
On Tue, Oct 21, 2008 at 12:35:00PM -0200, Rogério Brito wrote:
I don't know if you would call it a bug or not. Fundamentally,
yanking out a USB stick without unmounting it first is dangerous, and
can lead to data loss.
At least sync'ing...
I'm loath to suggest just syncing, because if
tags 502323 +pending
thanks
Thank you for reporting the typo in the changelog; it will be fixed in
the next release.
- Ted
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Fri, Oct 17, 2008 at 06:39:55PM +0400, Kondrat Pushkarev wrote:
Package: e2fsprogs
Version: 1.41.2-1
Severity: critical
Justification: breaks unrelated software
blkid returns true even if specified device does not exist (it should
return 2). This appears to be a new bug in lenny, as
severity 502541 normal
thanks
On Fri, Oct 17, 2008 at 10:14:41PM +0400, Peter Bray wrote:
Hi Ted,
Well, it broke one of my custom boot scripts which relied on the
return value to determine if a usb device was up or not. That script
broke when I upgraded to lenny, leaving my system
On Sun, Oct 12, 2008 at 02:00:19PM +0200, Mike Hommey wrote:
There seems to be no such function, which would be equivalent to
ext3_bg_num_gdb in fs/ext3/balloc.c in the kernel source.
Why would you find such a function useful in a user application? What
are you trying to do?
tags 498033 +pending
severity 498033 minor
thanks
Andrian,
Thanks for the proposed patch! Actually, you want to check to see if
theimage is NULL before the recursion check; otherwise, the in_routine
variable gets left set non-zero, which disables the command for the
rest of the xzgv run.
On Tue, Sep 09, 2008 at 11:32:25PM +1000, Trent W. Buck wrote:
On Tue, Sep 09, 2008 at 08:59:02AM -0400, Theodore Tso wrote:
Also, since this bug report falls into the Doctor, doctor, it hurts
when I do that --- then don't that!,
The situation is that I do this:
xzgv `mainline -v -c
On Wed, Sep 10, 2008 at 12:41:19AM +1000, Trent W. Buck wrote:
If xzgv is given a list of files it should just display the files
right away, and not give you an empty image. [...] So I'm a bit
confused how you are running into this situation given the scenario
you have described.
Hmm,
tags 498100 +pending
tags 498101 +pending
tags 498102 +pending
tags 498103 +pending
thanks
Thanks for pointing these spelling errors. I've committed fixes to
all of them to the maint branch of the e2fsprogs git repository.
- Ted
--
To
Hi,
Any progress on this your being able to figure out what is going on
your system?
As I said, this is almost certainly not an e2fsprogs bug, so I will
likely soon close this bug.
- Ted
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
On Thu, Sep 04, 2008 at 04:33:20PM +0200, Frans Pop wrote:
Looking at the diff between the Lenny and Sid versions, I wonder at the
dropped build dependencies on libdevmapper/libselinux1.
From the release notes:
The blkid library is now much more efficiently handling devicemapper
On Thu, Sep 04, 2008 at 12:55:23AM +0200, Frans Pop wrote:
The Depends on e2fsprogs-udeb are e2fslibs (= 1.41.0), libblkid1 (=
1.37), libc6 (= 2.7-1), libcomerr2 (= 1.37), libuuid1 (= 1.37)
The e2fsprogs-udeb used to depend on just libblkid1-udeb and libc6, all
the other dependencies are
Well, the fact that 'dd' can cause the system to crash, at least with
some kernels, makes it seem pretty conclusive to me. My guess is that
it is some combination of kernel and hardware problem, and exactly
when it happens may be triggered by timing or order of disk accesses,
or something very
tags 497010 +pending
thanks
On Fri, Aug 29, 2008 at 05:18:02PM +1000, Alex Samad wrote:
My group libuuid is in my ldap DB, install of package fails unless I
place it in my /etc/group file
Whilst checking the postinst file I also notice you check for user in
/etc/passwd - my user is kept in
severity 496956 normal
thanks
Sounds like your kernel is crashing when a certain part of the disk is
being accessed. If a userspace program can cause a system crash, by
definition that's a kernel bug, not a userspace bug. The fact that
the system is crashing on you any way if you abort e2fsck
tags 495830 +pending
thanks
On Wed, Aug 20, 2008 at 03:30:34PM -0400, Dale Harris wrote:
Package: e2fsprogs
Version: 1.41.0-3
Severity: normal
Perhaps I'm just doing this wrong, but it seems it should work:
arrr:/test# e2image /dev/rootvg/tmplv tmplv.img
e2image 1.41.0 (10-Jul-2008)
On Fri, Aug 01, 2008 at 02:13:31PM +0200, Marco d'Itri wrote:
On Aug 01, Guido Günther [EMAIL PROTECTED] wrote:
Reason is that findfs and friends query /etc/blkid.tab to find the
device matching the UUID. Since blkid.tab has things like
/dev/.static/dev/hda7 (no idea why blkid picked that
severity 493216 important
thanks
On Fri, Aug 01, 2008 at 08:24:38AM -0400, Theodore Tso wrote:
On Fri, Aug 01, 2008 at 02:13:31PM +0200, Marco d'Itri wrote:
On Aug 01, Guido Günther [EMAIL PROTECTED] wrote:
Reason is that findfs and friends query /etc/blkid.tab to find the
device
On Fri, Aug 01, 2008 at 03:30:08PM +0200, Marco d'Itri wrote:
On Aug 01, Theodore Tso [EMAIL PROTECTED] wrote:
Am I right in assuming that udev 0.125 is not something that you guys
are planning on trying to slide into Lenny?
No, both me and the d-i team definitely expect it to be in lenny
tags 491620 +pending
thanks
On Sun, Jul 20, 2008 at 11:07:06PM +0100, Pedro Ribeiro wrote:
In POT file there are two different references to the maximum journal
size, the first in a message near line 4402 (message from
misc/util.c:228) and the second one in line 4424 (message from
On Wed, Jul 16, 2008 at 11:16:47AM +0200, Peter 1 Oberparleiter wrote:
Ok, now I understand the core of your point. I must admit that with my
Linux background I haven't been aware of this association at all. I'm
wondering if some kind of documentation would help clear up any confusion
about
Holger,
It is deliberate that the cache is not flushed after a device is
remoed. So just because you are seeing stale entries in blkid does
*not* mean that there are any problems. Before an entry is used, it
will be validated.
Keep in mind that blkid's main function is not to show you all of
On Sat, Jul 12, 2008 at 10:29:46AM -0400, Theodore Tso wrote:
On Sat, Jul 12, 2008 at 03:45:25PM +0200, Harald Dunkel wrote:
blkid -c /dev/null -t LABEL=usbdos
dies with segmentation fault. The labeled filesystem
is available, but not mounted.
I can't replicate this. Can you
On Sun, Jul 13, 2008 at 06:53:25PM +0930, Kevin Shanahan wrote:
Package: e2fsprogs
Version: 1.41.0-1
Thanks for reporting this bug. I will shortly be releasing a fixed
e2fsprogs with this patch.
- Ted
From
severity 490540 normal
thanks
On Sat, Jul 12, 2008 at 03:59:25PM +0200, Harald Dunkel wrote:
I ran blkid as a regular user. If I run it as root
then the core dump is gone.
Surely its OK to decrease the severity of this br.
I suspect you filed this against the wrong bug report. You carbon
On Sat, Jul 12, 2008 at 03:45:25PM +0200, Harald Dunkel wrote:
blkid -c /dev/null -t LABEL=usbdos
dies with segmentation fault. The labeled filesystem
is available, but not mounted.
I can't replicate this. Can you replicate it this now? If so, please
save the /etc/blkid.tab file to make it
On Sat, Jul 12, 2008 at 01:54:08PM +0200, Harald Dunkel wrote:
Package: e2fsprogs
Version: 1.41.0-1
Severity: wishlist
It would be very nice if blkid could tell whether a partition
or a device is mounted or in use (e.g. part of a logical volume).
Well, that really isn't part of blkid's
tag 490527 +pending
thanks
On Sat, Jul 12, 2008 at 01:33:48PM -0400, Theodore Tso wrote:
On Sat, Jul 12, 2008 at 01:54:08PM +0200, Harald Dunkel wrote:
Package: e2fsprogs
Version: 1.41.0-1
Severity: wishlist
It would be very nice if blkid could tell whether a partition
or a device
Thanks very much for your patch! My apologies for the delay in
getting this patch applied and released. But it's in the 0.9+svn40-1,
which I just uploaded into unstable.
Regards,
- Ted
tags 490003 +pending
thanks
On Wed, Jul 09, 2008 at 10:03:32AM +0200, Yann Dirson wrote:
Package: e2fsck-static
Version: 1.40.11-1
Severity: wishlist
This package recommends a bunch of statically-linked shells, but this list
does not include bash-static.
--
To UNSUBSCRIBE, email to
tags 471977 +pending
thanks
On Fri, Mar 21, 2008 at 03:34:45PM +0100, Michael Banck wrote:
I wonder whether it would be possible to tell mk2fs to use different
defaults for block and inode size if a Hurd-owned partition (i.e., the
user passed -o hurd) is requested. The ext2fs server in the
On Tue, Jun 24, 2008 at 04:29:25PM +0200, Peter Rabbitson wrote:
Currently the man-page of mkfs.ext2 reads:
...This is typically be stride-size * N, where N is the number of data disks
in the RAID (e.g. RAID 5 N+1, RAID 6 N+2)...
which actually should be:
...(e.g. RAID 5 N-1, RAID 6
On Wed, Jul 09, 2008 at 09:20:52AM -0700, Stephen Powell wrote:
The structure I sent to you maps the CMS label record. For FBA
devices, the label record is the second 512-byte block of the
minidisk. For CKD devices, the label record is cylinder 0, track 0,
record 3, which would be the third
I've floated your request to some colleagues of mine at the IBM Linux
Technology Center, and one of them sent back this reply.
Have spent some time mulling this over with some VM sysprog
buddies of mine we've come to the conclusion that it is not clear
what this request is trying to
FYI,
I just got connected to the right people in the zSeries Linux group in
Germany, and they are suggesting to me that the CMS label is really
more of a partition thing, and the right fix may be in the kernel, to
restrict the partition seen by mke2fs to exclude the RECOMP area.
Their only
I've looked at the patch, and there are too many acronyms!
Where is this CMSFSADT label supposed to be found? According to some
comments, for FBA DASD's it is located at offset 512 bytes. I know
that DASD is a mainframe-encrypted word for disk, but what is FBA?
And then there are these strang
On Sat, Jul 05, 2008 at 07:19:21AM +0200, Harald Dunkel wrote:
Would you mind to increase the priority of this report? I've
got a small Linutop PC (booting from a USB memory stick).
Now I have to wipe out blkid.tab before every reboot, or it
doesn't :-(.
I've just released e2fsprogs
tags 487298 +pending
thanks
On Fri, Jun 20, 2008 at 04:44:28PM -0400, Ariel wrote:
I haven't figured out what pattern of -t tests is needed to trigger it.
Adding or removing one might make it stop crashing, and changing a
random to a fixed number also changes it.
Creating more than 8 -t
tags 488663 +pending
thanks
I've applied the following two patches to e2fsprogs's git repository.
- Ted
From b4d5105b2527a5279cf5b885b957e1e07a53e725 Mon Sep 17 00:00:00 2001
From: Theodore Ts'o [EMAIL PROTECTED]
Date: Sun, 6 Jul 2008 20:24:29 -0400
On Mon, Jun 16, 2008 at 08:44:23AM -0700, Stephen Powell wrote:
Package: e2fsprogs
Version: 1.39+1.40-WIP-2006.11.14+dfsg-2etch1
Severity: wishlist
This is an enhancement request that applies to the s390 and s390x
architectures only. Currently, when mke2fs is run against the
single
On Thu, Jul 03, 2008 at 11:47:17PM +0200, Philippe Coval wrote:
Package: e2fsprogs
Version: 1.40.8-2
Followup-For: Bug #475167
I am also affected, by this bug for a few weeks, here follows
the traces your were asking for
I am about to update to more recent versions in unstable (and
On Tue, Jul 01, 2008 at 08:47:58AM +0200, Paul Slootman wrote:
I created the external journal without specifying the blocksize, not
realizing that I needed to. Perhaps the blocksize parameter should be
mandatory when creating an external journal...
Oh, I bet I know what happened. The external
1 - 100 of 235 matches
Mail list logo
