mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.19-rc1,2 + ext3 data=journal: data loss on unmount
Date: Fri, 29 Nov 2002 09:45:59 +1100	[thread overview]
Message-ID: <3DE69CA7.5070601@cyberone.com.au> (raw)
In-Reply-To: <1038502327.10021.17.camel@irongate.swansea.linux.org.uk>

Alan Cox wrote:

>On Thu, 2002-07-18 at 07:12, Piggin, Nick wrote:
>
>>mount /mnt/backup
>>tar cvf $FILENAME directory
>>bzip2 $FILENAME
>>umount /mnt/backup
>>
>>Upon remounting and inspection, the resulting bzip2 file is corrupted every
>>time. Adding a sync after bzip2 corrects the problem.
>>
>
>That sounds like a bug in the core code somewhere since the flush should
>have happened automatically on umount. Does 2.4.19 proper show this on
>your box (or 2.4.20-rc) ? [I'd suspect yes but would like to be sure]
>
>
For those that don't remember, $FILENAME is in /mnt/backup and
it was 100% repeatable (ie. a data corruption bug). Alan,
unfortunately I can't do a lot of testing with the box now. I
might be able to give it a try when 2.4.20 comes out, or someone
else might be able to. Directory was only a meg or two IIRC
so it shouldn't be much hasstle for someone with a spare ext3
partition.

Nick


  reply	other threads:[~2002-11-28 22:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-18  6:12 Piggin, Nick
2002-07-18 16:49 ` Bill Davidsen
2002-11-28 16:52 ` Alan Cox
2002-11-28 22:45   ` Nick Piggin [this message]
2002-11-29  1:30   ` Nick Piggin
2002-07-18  6:22 Piggin, Nick

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=3DE69CA7.5070601@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®