linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 13292] New: ext4 without journal reproductible file corruption
Date: Wed, 13 May 2009 09:22:43 GMT	[thread overview]
Message-ID: <bug-13292-13602@http.bugzilla.kernel.org/> (raw)

http://bugzilla.kernel.org/show_bug.cgi?id=13292

           Summary: ext4 without journal reproductible file corruption
           Product: File System
           Version: 2.5
    Kernel Version: 2.6.29.3
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: ext4
        AssignedTo: fs_ext4@kernel-bugs.osdl.org
        ReportedBy: thibm@free.fr
        Regression: No


Created an attachment (id=21323)
 --> (http://bugzilla.kernel.org/attachment.cgi?id=21323)
The harddrive image to mount and chroot

Hi,

I found file(s) corruption using ext4 without journal, on two different
hardware (a dell vostro 1700, 64 bits archlinux + 64 bits jaunty, perso kernel
2.6.29.3 and an acer aspire one a110, ssd, 32 bits archlinux, same kernel
version).


The problem can be reproduced using the hdd image in attachment. This file is
an ext4 without journal image of a minimal archlinux 64 system.

Step to reproduce :

A-

1/ extract the archive on a 64 bits system running 2.6.29.3
2/ mount the .img as ext4, loopback
3/ chroot in the mounted directory
4/ execute "locale-gen"
5/ execute "locale". The result is ok
6/ have a look at /usr/lib/locale/locale-archive file (with vi or other editor)
7/ exit chroot
8/ umount hd image

B-

1/ mount again the hd image
2/ chroot again
3/ execute "locale". There are 3 errors at the beginning, the output is not the
same as previously
4/ look at /usr/lib/locale/locale-archive, the content is not the same !


Reproduce these steps with a journal (tune2fs -O has_journal, fsck -f) and
you'll see the file locale-archive and the output of locale command are
consistants between mount/umount.

The file locale-archive is not the only affected. On other system, that was
nvidia kernel module which was corrupted between installation and reboot.


Regards,

Thibault

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

             reply	other threads:[~2009-05-13  9:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-13  9:22 bugzilla-daemon [this message]
2009-05-13 23:10 ` [Bug 13292] ext4 without journal reproductible file corruption bugzilla-daemon
2009-05-14 14:14 ` bugzilla-daemon
2009-05-14 20:07 ` bugzilla-daemon
2009-05-20  1:02 ` bugzilla-daemon
2009-05-20 17:36 ` bugzilla-daemon
2009-05-27 19:23 ` bugzilla-daemon
2009-05-28 21:16 ` bugzilla-daemon
2009-07-21  9:02 ` 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-13292-13602@http.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).