public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Santiago Garcia Mantinan <manty@manty.net>
To: Andrew Morton <akpm@zip.com.au>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: ext3-2.4-0.9.10
Date: Mon, 24 Sep 2001 14:16:38 +0200	[thread overview]
Message-ID: <20010924141638.A2275@man.beta.es> (raw)
In-Reply-To: <3BAECC4F.EF25393@zip.com.au>
In-Reply-To: <3BAECC4F.EF25393@zip.com.au>

Hi!

After testing this new patch on 2.4.10 I have detected a problem when trying
to convert mounted partitions to ext3.

The problem is that on umounting the partition, with 2.4.10 kernel, the
has_journal feature mark is removed, so the device is not detected as having
journal on next mount.

Creating journals (converting to ext3) on partitions that are not mounted
works ok.

Following is a practical demonstration of this in case I didn't explain
myself well...

pul:/# grep var /etc/fstab
/dev/hda7 /var auto rw 0 2
pul:/# mount|grep var
/dev/hda7 on /var type ext2 (rw)
pul:~# tune2fs -l /dev/hda7|grep -i journal
pul:~# ls -l /var/.journal
ls: /var/.journal: No such file or directory
pul:~# tune2fs -j /dev/hda7
tune2fs 1.24a (02-Sep-2001)
Creating journal inode: done
This filesystem will be automatically checked every 20 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.
pul:~# tune2fs -l /dev/hda7|grep -i journal
Filesystem features:      has_journal filetype sparse_super
Journal UUID:             <none>
Journal inode:            12
Journal device:           0x0000
pul:~# ls -l /var/.journal
-rw-------    1 root     root      8388608 sep 24 13:39 /var/.journal
pul:/# umount /var
pul:/# tune2fs -l /dev/hda7|grep -i journal
pul:/# mount /var
pul:/# mount|grep var
/dev/hda7 on /var type ext2 (rw)
pul:/# ls -l /var/.journal
-rw-------    1 root     root      8388608 Sep 24 13:39 /var/.journal

Regards...
-- 
Manty/BestiaTester -> http://manty.net

  reply	other threads:[~2001-09-24 12:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-24  6:01 ext3-2.4-0.9.10 Andrew Morton
2001-09-24 12:16 ` Santiago Garcia Mantinan [this message]
2001-09-24 17:47   ` ext3-2.4-0.9.10 Andreas Dilger
2001-09-24 17:14 ` ext3-2.4-0.9.10 Robert Love
2001-09-24 17:16 ` ext3-2.4-0.9.10 Tom Rini
2001-09-24 17:19   ` ext3-2.4-0.9.10 Andrew Morton
2001-09-24 17:29     ` ext3-2.4-0.9.10 Tom Rini
2001-09-24 17:21   ` ext3-2.4-0.9.10 Stephen C. Tweedie
  -- strict thread matches above, loose matches on Subject: below --
2001-09-24 21:35 ext3-2.4-0.9.10 J Troy Piper
2001-09-24 21:54 ` ext3-2.4-0.9.10 Andrew Morton
2001-09-24 22:39   ` ext3-2.4-0.9.10 Andreas Dilger

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=20010924141638.A2275@man.beta.es \
    --to=manty@manty.net \
    --cc=akpm@zip.com.au \
    --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