On Sun, Aug 02, 2020 at 07:23:35PM +0200, Andreas Beckmann wrote:
>
> e2fsprogs/experimental started to FTBFS when GCC 10 was made the default
> compiler:
>
Thanks for the bug report. This is fixed in e2fsprogs 1.45.6-1 by:
commit 336c440ccea8f94b0728f881cddee84f730e7cc7
Author: Lukas Czerner
On Sun, Jul 26, 2020 at 10:58:04PM +0200, Andreas Beckmann wrote:
> Source: e2fsprogs
> Version: 1.45.6-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> Control: found -1 1.46~WIP.2019.10.03-1
>
> Hi,
>
> libblkid-dev recently
On Thu, Mar 20, 2014 at 05:30:32PM +, Ben Hutchings wrote:
>
> It looks like ext2 and ext3 would always initialise i_version to 1 in
> memory; does it matter that you're changing that to 0 for Hurd
> filesystems?
No, NFS only cares that the i_version number has changed, and it's
mainly import
On Thu, Mar 20, 2014 at 01:10:48AM -0700, Christoph Hellwig wrote:
> On Wed, Mar 19, 2014 at 11:27:57PM -0600, Andreas Dilger wrote:
> > Probably worthwhile to make those !EXT4_OS_HURD checks likely()?
Yes, and I was planning on optimizing the checks a bit more, but it
makes sense to do that in a
tags 585041 +pending
thanks
On Tue, Jun 08, 2010 at 06:20:00PM +0200, Michael Biebl wrote:
> Package: e2fsprogs
> Version: 1.41.12-2
>
> the last release that shipped initrd-tools was etch and it was removed
> afterwards. I'd say it's about time that e2fsprogs removes the obsolete
> /usr/share/in
On Wed, Jun 30, 2010 at 12:32:19PM +0200, John Hughes wrote:
>
> 1. fsck refuses to work if the journal device is open
We can try doing an exclusive open on the journal device, and refuse
if the journal is active. That's a good idea.
> 2. tune2fs -f -O ^has_journal modifies the filesystem b
On Wed, Jun 30, 2010 at 12:17:09PM +0200, John Hughes wrote:
> Actualy this is even worse than I thought.
>
> If an external journal gets destroyed there appears to be no way to
> fsck the filesystem.
>
> I have an ext3 filesystem on /dev/group-a/ums which has a journal on
> /dev/flash/ums-journa
On Tue, Jun 29, 2010 at 04:30:42PM +0200, John Hughes wrote:
> Package: e2fsprogs
> Version: 1.41.12-2
> Severity: normal
>
> On a lvm2 based system I have an ext3 fileystem with an external journal.
>
> I want to use lvm2s snapshot facilities to do online backups and fscks.
>
> So I create a sn
On Sun, Jun 27, 2010 at 04:08:42PM -0700, Kenyon Ralph wrote:
> This bug is also present when doing netboot squeeze installs right now
> from the US http mirrors. I think it is also causing the installer to
> fail to detect my hard drive, which already has several ext4
> partitions.
Probably would
On Mon, Jun 21, 2010 at 08:11:59AM +0200, Thomas Schwinge wrote:
> Hello!
>
> On Sat, Jun 19, 2010 at 12:18:38PM +0200, Erwan David wrote:
> > Package: e2fsprogs
> > Version: 1.41.12-1
> > Severity: important
> >
> >
> > When trying to format a disk (either ext2 or ext3) I get
> >
> > mkfs.ext3
On Mon, Jun 14, 2010 at 12:32:38PM -0400, Matthias Bannach wrote:
> The problem still occurred on an updated squeeze system as of today noon EST
> Jun 14th:
E2fsprogs 1.41.12-2 hasn't hit squeeze yet. It's been held up because
of util-linux-ng:
http://release.debian.org/migration/testing.pl?pack
On Thu, May 27, 2010 at 05:58:12PM -0700, Elliott Mitchell wrote:
>
> Oy vey! I'm inclined to suggest that if this really does happen, that
> sounds like a bug... I could understand funky occurances if after
> reloading, the kernel can no longer find the FS data structures (device
> was erased),
On Mon, May 24, 2010 at 03:11:23PM -0700, Elliott Mitchell wrote:
> Any update?
I continue to think this is hopelessly complex and not worth the
effort.
If you hate precautionary checks so much, then turn them off. The
tools for doing this are within your hands. Or do them using a LVM
snapshot.
On Sat, Feb 20, 2010 at 09:05:37PM +0100, Goswin von Brederlow wrote:
>
> I'm experimenting with running fsck for / from the initramfs to avoid
> the extra reboot when the filesystem is changed. The initramfs has no
> /etc/mtab (as that is obsolete anyway) but /proc/mounts. I think it
> would be g
On Thu, Mar 25, 2010 at 12:55:50AM -0700, Elliott Mitchell wrote:
>
> Which is why I wasn't writing about the mount count. I was writing about
> the check interval/check time. With systems that reboot less than once a
> month, the mount count will never be reached. Instead it will be the
> check i
On Wed, Mar 24, 2010 at 05:29:58PM -0700, Elliott Mitchell wrote:
> Package: e2fsprogs
> Version: 1.41.3-1
>
> Subject tells the story. Why are mere /precautionary/ filesystem checks
> allowed to slow a system booting so much? ie the ones triggered by either
> the mount count or check time exceedi
On Wed, Mar 17, 2010 at 12:16:01PM +0100, Wouter Verhelst wrote:
> Package: e2fsprogs
> Version: 1.41.10-1
> Severity: normal
>
> A few days back, I tried to run 'resize2fs -M' on an ext4 filesystem.
> While it was running, I accidentally hit ^C in its xterm window (I was
> confused about which wi
On Sun, Mar 14, 2010 at 05:14:51PM -0700, Kees Cook wrote:
>
> I noticed that the debian/rules contains "-fno-stack-protector". While
> this used to be needed a while back, this is no longer required, as the
> stack protection code will be statically compiled into the static e2fsprogs
> correctly
tags 564084 +pending
thanks
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=564084
On Thu, Jan 07, 2010 at 10:57:25PM +0700, Anon Sricharoenchai wrote:
>
> *** Please type your report below this line ***
> "logdump -b" command in debugfs show incorrect allocation status
> in block bitmap
Thank
On Thu, Mar 04, 2010 at 12:18:53PM +0100, Jan Fricke wrote:
> Package: e2fsprogs
> Version: 1.41.10-1
> Severity: important
>
> After "e2fsck -D" a second e2fsck reports that in some directories
> "." and ".." are not the first entries. This happens in directories
> with entries beginning with "%"
severity 559776 normal
thanks
On Mon, Dec 07, 2009 at 01:08:12AM +, peter green wrote:
> package: e2fsprogs
> severity: critical
> justification: breaks the entire system
Your system is broken already because it doesn't have a usable RTC.
Having correct system time is important! Indeed, ther
severity 557636 normal
thanks
On Mon, Nov 23, 2009 at 02:09:18PM +0100, Bastian Blank wrote:
> Package: e2fsprogs
> Version: 1.41.9-1
>
> fsck.ext3 enforces synchronized clocks, but does not pull anything in to
> actually make sure that they are.
This only applies in virtualized environments, be
On Sun, Nov 22, 2009 at 11:29:28AM +1000, Kel Modderman wrote:
> > It's gross as all
> > heck that the wpa_gui is using a facility originally from wpa_debug.c
> > to communicate with wpa_supplicant. That's an upstream problem, yes
> > and they ought to be ashamed of themselves. :-)
>
> No idea w
On Wed, Aug 05, 2009 at 08:30:08AM +1000, Kel Modderman wrote:
> > I'm using wpa_supplicant via NetworkManager (autostarted by dbus).
> > I get a lot (multiple hundreds) of those messages in my /var/log/syslog:
> >
> > Aug 4 02:24:26 pluto wpa_supplicant[2781]: CTRL-EVENT-SCAN-RESULTS
> > Aug 4
24 matches
Mail list logo
