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:

mkfs.xfs /dev/vdb5
mount /dev/vdb5 /mnt/scratch
touch /mnt/scratch/foo
filefrag /mnt/scratch/foo
/mnt/scratch/foo: 1 extent found

While xfs_bmap gets the right results:

qemu1:~/xfstests-dev# xfs_bmap /mnt/scratch/foo 
/mnt/scratch/foo: no extents

When actually having extents it seems fine:

qemu1:~/xfstests-dev# echo "foo" > /mnt/scratch/foo 
qemu1:~/xfstests-dev# filefrag /mnt/scratch/foo 
/mnt/scratch/foo: 1 extent found
qemu1:~/xfstests-dev# xfs_bmap /mnt/scratch/foo 
/mnt/scratch/foo:
        0: [0..7]: 96..103

The behaviour is similar on ext3, but no tool to verify it there:

qemu1:~/xfstests-dev# mkfs.ext3 /dev/vdb5
mount /dev/vdb5 /mnt/scratch/
qemu1:~/xfstests-dev# touch /mnt/scratch/foo
qemu1:~/xfstests-dev# filefrag /mnt/scratch/foo 
/mnt/scratch/foo: 1 extent found


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.31-rc5 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/bash

Versions of packages e2fsprogs depends on:
ii  e2fslibs                      1.41.3-1   ext2 filesystem libraries
ii  libblkid1                     1.41.3-1   block device id library
ii  libc6                         2.9-12     GNU C Library: Shared libraries
ii  libcomerr2                    1.41.3-1   common error description library
ii  libss2                        1.41.3-1   command-line interface parsing lib
ii  libuuid1                      1.41.3-1   universally unique id library

e2fsprogs recommends no packages.

Versions of packages e2fsprogs suggests:
pn  e2fsck-static                 <none>     (no description available)
pn  gpart                         <none>     (no description available)
pn  parted                        <none>     (no description available)

-- no debconf information



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

Reply via email to