Your message dated Mon, 23 Feb 2009 13:32:03 +0000
with message-id <[email protected]>
and subject line Bug#497984: fixed in libcitadel 7.41-1
has caused the Debian Bug report #497984,
regarding e2fsprogs: better support for loopbacks
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.)
--
497984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497984
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: e2fsprogs
Version: 1.41.0-3
Severity: normal
Is it possible to add better support for loopbacks? Meaning, figure out
which is the real file/device the loopback is using?
I accidentally had a fs mounted via one loopback, then using a different
loopback on the same device ran fsck, and then resize2fs (to make it
larger).
The fsck told me:
ext3 recovery flag is clear, but journal has data.
Run journal anyway<y>?
I told it no, and then had it clear the journal.
I then ran resize2fs and mounted it, and only then realized I had it
mounted already! (Note that I did not write anything whatsoever on the
mounted fs, just whatever mount does on it's own.)
I unmounted both and ran fsck again and it found:
Block bitmap differences (about 20 of them), and then Free blocks count wrong
again about 20.
Otherwise everything seem OK, but is it possible some file got currupted
and I would not know?
So my first question is: Is everything actually OK? I have a backup of
the entire fs, but it would be a huge amount of work to get it (the
backup is in the form of unused area on an lvm, I moved all the data to a
new hard disk, but the old is still sitting there in 3 pieces - if I can
figure out the offsets and stich it back together).
And my second question, which is actually the bugreport, is can you do
the equivalent of:
losetup -a
And use both the base device/file, along with the loopback one to detect if
it's mounted already? (That way if two loopbacks are using the same
device it'll detect it.)
And, BTW: loopbacks don't seem to support fsync, because when
fsck.ext3 -D, or resize2fs finsish, I ran sync and it worked for a
good minute or two. Can you run a prophylactic sync after those tools,
just in case? Or perhaps just for loopback devices?
Thank you,
-Ariel
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.25
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages e2fsprogs depends on:
ii e2f 1.41.0-3 ext2 filesystem libraries
ii lib 1.39+1.40-WIP-2006.11.14+dfsg-2etch1 block device id library
ii lib 2.7-6 GNU C Library: Shared libraries
ii lib 1.39+1.40-WIP-2006.11.14+dfsg-2etch1 common error description library
ii lib 1.39+1.40-WIP-2006.11.14+dfsg-2etch1 command-line interface parsing lib
ii lib 1.39+1.40-WIP-2006.11.14+dfsg-2etch1 universally unique id library
e2fsprogs recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libcitadel
Source-Version: 7.41-1
We believe that the bug you reported is fixed in the latest version of
libcitadel, which is due to be installed in the Debian FTP archive:
libcitadel-dev_7.41-1_amd64.deb
to pool/main/libc/libcitadel/libcitadel-dev_7.41-1_amd64.deb
libcitadel1-dbg_7.41-1_amd64.deb
to pool/main/libc/libcitadel/libcitadel1-dbg_7.41-1_amd64.deb
libcitadel1_7.41-1_amd64.deb
to pool/main/libc/libcitadel/libcitadel1_7.41-1_amd64.deb
libcitadel_7.41-1.diff.gz
to pool/main/libc/libcitadel/libcitadel_7.41-1.diff.gz
libcitadel_7.41-1.dsc
to pool/main/libc/libcitadel/libcitadel_7.41-1.dsc
libcitadel_7.41.orig.tar.gz
to pool/main/libc/libcitadel/libcitadel_7.41.orig.tar.gz
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.
Michael Meskes <[email protected]> (supplier of updated libcitadel 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.8
Date: Fri, 20 Feb 2009 16:49:05 +0100
Source: libcitadel
Binary: libcitadel1 libcitadel1-dbg libcitadel-dev
Architecture: source amd64
Version: 7.41-1
Distribution: unstable
Urgency: low
Maintainer: Debian Citadel Team <[email protected]>
Changed-By: Michael Meskes <[email protected]>
Description:
libcitadel-dev - Development files for libcitadel1
libcitadel1 - Citadel toolbox
libcitadel1-dbg - Debugging symbols for libcitadel1
Closes: 497984
Changes:
libcitadel (7.41-1) unstable; urgency=low
.
* New upstream version, closes: #497984
* Changed watch file to account for an additional letter in the version
number if present.
Checksums-Sha1:
eaf69d58d69c189a7de29c96800612d587b6f4e0 1193 libcitadel_7.41-1.dsc
eda4342fae91aa2e4fb646203c99d66734d9ecfd 521633 libcitadel_7.41.orig.tar.gz
1d5b9df9afb5689aee03adac07bb5fd4299ed68a 3133 libcitadel_7.41-1.diff.gz
f424c8f85dfceb66c341c7bbc375a45e64541178 53822 libcitadel1_7.41-1_amd64.deb
22c77d03d6da7b31d9f5ded060e072a0be9868c3 85030 libcitadel1-dbg_7.41-1_amd64.deb
ed995fc305e13f50879bdc189b31c1c98ec82abc 63666 libcitadel-dev_7.41-1_amd64.deb
Checksums-Sha256:
7d6bfac47dbbafaca2a0dd41d453cc8caf45a71c5f12b3df5015a7a0fc0cee58 1193
libcitadel_7.41-1.dsc
781daf79d951d5a3c6a55897672a4e3638900751974ff15a104d67ac2ab4d55c 521633
libcitadel_7.41.orig.tar.gz
3ab2a6f16be0f8326bd684cc3348c5c40bc7925648b5a269d4fc95b973237c2a 3133
libcitadel_7.41-1.diff.gz
d9387b05cc842f0e30cd5c016497c506d8e92edfba44fbb7e69f0f6c05565f86 53822
libcitadel1_7.41-1_amd64.deb
f22b0abe67efaf1ac5a2dd52f2f85ba342661aa2f95471c00af622e00238d76a 85030
libcitadel1-dbg_7.41-1_amd64.deb
20ada47165e3cb72fedffb2eeecfcc031f32752f44acbbb12f89cac27c0a8b9e 63666
libcitadel-dev_7.41-1_amd64.deb
Files:
a3adc939227966849957af0e2c65986b 1193 libs extra libcitadel_7.41-1.dsc
387f89799194fe07838aed3966bce921 521633 libs extra libcitadel_7.41.orig.tar.gz
4f5bef42152fd59d9a2e05eb3a80da95 3133 libs extra libcitadel_7.41-1.diff.gz
ed43cebb733aa15a96691ae14e8021e2 53822 libs extra libcitadel1_7.41-1_amd64.deb
81376f2d7af518529e00f6f35ed30346 85030 libdevel extra
libcitadel1-dbg_7.41-1_amd64.deb
702b4bad90e7a31946e7a3f06d63189b 63666 libdevel extra
libcitadel-dev_7.41-1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iD8DBQFJoqR+VkEm8inxm9ERAoewAJ4lIJNzyNmTXwk0xqAnMXQMbZhuZwCdHxUB
/kGN64PsCRzwnneAA/dvqgM=
=7OkG
-----END PGP SIGNATURE-----
--- End Message ---
