Re: ext2 vs ext3?

On 2006-01-19, Rick Moen <rick@xxxxxxxxxxxxxx> wrote:
> General Schvantzkoph <schvantzkoph@xxxxxxxxx> wrote:
>
>> EXT3 is EXT2 plus journaling. No one uses plain EXT2 anymore....
>
>:r! mount
>
> /dev/sda5 on / type ext3 (rw,errors=remount-ro)
> /dev/sda1 on /boot type ext2 (rw,noexec,nosuid,nodev)
> /dev/sdb1 on /home type ext3 (rw,nosuid,nodev)
> /dev/sdb5 on /tmp type ext2 (rw,nosuid,nodev,noatime)
> /dev/sdb8 on /usr type ext2 (rw,nodev)
> /dev/sda9 on /usr/local type ext3 (rw)
> /dev/sdb7 on /var type ext3 (rw,nosuid,nodev,noatime)
> /dev/sda8 on /var/log type ext2 (rw,nosuid,nodev,noatime)
> proc on /proc type proc (rw)
> devpts on /dev/pts type devpts (rw,gid=5,mode=620)
> tmpfs on /dev/shm type tmpfs (rw)
> usbfs on /proc/bus/usb type usbfs (rw)
>
> Remind me, again: _Why_ exactly would I be wanting journaling on /tmp?

The primary advantage of ext3 is it allows faster reboot
after a crash. Instead of having to run e2fsck, the system
simply recovers from the journal (a couple of seconds at
most) and boots up.

I have a _hunch_ that the journal also _might_ slightly
reduce the risk of data loss when booting back from a crash.
You _might_ have something you were working on in /tmp when
it crashed.

I think it was when I was still running HatRed 9, I switched
over from ext2 to ext3 with only a few file edits, a reboot
to make the change take effect, and one more reboot because
I hadn't put the ext3 module in initrd or something like
that.

IIRC, there may be a small performance penalty from using
ext3 in some heavy I/O situations.

--
Robert Riches
spamtrap42@xxxxxxxxxxx
(Yes, that is one of my email addresses.)
.

Relevant Pages