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



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to