Your message dated Sat, 28 Oct 2006 15:47:17 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#212989: fixed in gpart 0.1h-4.1
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: gpart
Version: 0.1h-3
Severity: normal
Tags: patch
I've found that gpart doesn't detect my ext3 partition. It should
appear as ext2. After looking at the source, I've found that
module gm_ext2 discards any fs with mount_count>max_mount_count+20.
Usually ext3 filesystems have max_mount_count=-1, because they have a
journal to avoid frequent fscks, so this condition is almost always
true.
I include a trivial patch which changes this and allows ext3 partitions
to be detected as ext2.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux athlon 2.4.22 #5 Fri Aug 29 21:13:01 CEST 2003 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages gpart depends on:
ii libc6 2.3.2-8 GNU C Library: Shared libraries an
-- no debconf information
diff -u -x '*.o' -r gpart-0.1h/src/gm_ext2.c gpart.test3/src/gm_ext2.c
--- gpart-0.1h/src/gm_ext2.c 2001-02-07 19:08:08.000000000 +0100
+++ gpart.test3/src/gm_ext2.c 2003-09-27 13:08:16.000000000 +0200
@@ -121,9 +121,10 @@
/*
* current mount count shouldn't be greater than max+20
+ * but ext3 usually has s_max_mnt_count==-1
*/
- if (sb->s_mnt_count > sb->s_max_mnt_count + 20)
+ if ((sb->s_max_mnt_count!=-1)&&(sb->s_mnt_count > sb->s_max_mnt_count + 20))
return (1);
/*
--- End Message ---
--- Begin Message ---
Source: gpart
Source-Version: 0.1h-4.1
We believe that the bug you reported is fixed in the latest version of
gpart, which is due to be installed in the Debian FTP archive:
gpart_0.1h-4.1.diff.gz
to pool/main/g/gpart/gpart_0.1h-4.1.diff.gz
gpart_0.1h-4.1.dsc
to pool/main/g/gpart/gpart_0.1h-4.1.dsc
gpart_0.1h-4.1_i386.deb
to pool/main/g/gpart/gpart_0.1h-4.1_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Steve McIntyre <[EMAIL PROTECTED]> (supplier of updated gpart package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Sat, 28 Oct 2006 22:50:42 +0100
Source: gpart
Binary: gpart
Architecture: source i386
Version: 0.1h-4.1
Distribution: unstable
Urgency: medium
Maintainer: David Coe <[EMAIL PROTECTED]>
Changed-By: Steve McIntyre <[EMAIL PROTECTED]>
Description:
gpart - Guess PC disk partition table, find lost partitions
Closes: 212989 225578 246989 294836 322256 393039
Changes:
gpart (0.1h-4.1) unstable; urgency=medium
.
* NMU from the Cambridge BSP
* Rather than attempt to use the syscall(!) interface for 64-bit lseek,
simply compile to use the 64-bit VFS interface and use the normal
lseek calls. Let libc deal with the issues...
Closes: #225578, #294836, #393039.
* Applied the reiserfs 3.6 recognition patch from
ftp://ftp.namesys.com/pub/misc-patches/gpart-0.1h-reiserfs-3.6.patch.gz
Closes: #246989, #322256
* Recogniise ext3 filesystems as well as ext2. Thanks to Xisco Calafat
for the patch. Closes: #212989
Files:
9232c2b793258a6b44aac688fbffb4f8 539 admin optional gpart_0.1h-4.1.dsc
af413fbac154a6d138fa97af709d432e 9532 admin optional gpart_0.1h-4.1.diff.gz
4690231eda349138a7df012dad5a3bec 36310 admin optional gpart_0.1h-4.1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFFQ9xgfDt5cIjHwfcRAh4mAKCIFaaxpVQZ+Br2NGyCIhNAch6wSwCgn6gO
PKOlPzqERK0hPSx6DEzYF6g=
=kjQe
-----END PGP SIGNATURE-----
--- End Message ---
