All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 15666] New: e2fsck -fD on ext4 breaks
Date: Thu, 1 Apr 2010 10:36:07 GMT	[thread overview]
Message-ID: <bug-15666-13602@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=15666

           Summary: e2fsck -fD on ext4 breaks
           Product: File System
           Version: 2.5
    Kernel Version: 2.6.32.10
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: ext4
        AssignedTo: fs_ext4@kernel-bugs.osdl.org
        ReportedBy: khcha.n.el@gmail.com
        Regression: No


i did a e2fsck -fD on a ext4 filesystem, later a e2fsck -f complains a bunch of
errors. if i e2fsck -fy would end up a bunch of files go into lost+found or
simply lose trace.

Step to reproduce:
1. prepare a ext4 file system (dd if=/dev/zero of=test_ext4.img bs=1M
count=1000 && mkfs.ext4 test_ext4.img)
2. mount it (mount -t ext4 -o rw,loop test_ext4.img /mnt/tmp)
3. put some files on it, it seems to me that tiny files would cause the issue
(cp -r /home/$USER/.gconf /mnt/tmp)
4. un mount it (umount /mnt/tmp)
5. e2fsck -f test_ext4.img  all good
6. e2fsck -fD test_ext4.img seems fine
7. e2fsck -f test_ext4.img here comes trouble...

Components version:
Distro: Archlinux
Architecture: x86_64

kernel 2.6.32.10
e2fsck 1.41.10 (10-Feb-2009)
    Using EXT2FS Library version 1.41.10, 10-Feb-2009

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

             reply	other threads:[~2010-04-01 10:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-01 10:36 bugzilla-daemon [this message]
2010-04-01 10:37 ` [Bug 15666] e2fsck -fD on ext4 breaks bugzilla-daemon
2010-04-01 10:39 ` bugzilla-daemon
2010-04-01 11:51 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-15666-13602@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.