Since ext3 is just ext2 + a journal, it is possible to convert "on the fly." Read:
http://www.redhat.com/docs/manuals/linux/RHL-7.3-Manual/ref-guide/s1-filesys tem-ext3-convert.html Basically, login as "root" and enter: /sbin/tune2fs -j /dev/dasd??? Of course, the filesystem must not be mounted at the time! Then edit /etc/fstab and change the "ext2" to "ext3". If you ever have a problem that you think is ext3 related, you can "fall back" by changing the "ext3" to "ext2". All the metadata and user data is identical. ext3 IS ext2 + journalling, that is a "proper superset". -- John McKown Senior Systems Programmer UICI Insurance Center Applications & Solutions Team +1.817.255.3225 This message (including any attachments) contains confidential information intended for a specific individual and purpose, and its' content is protected by law. If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this transmission, or taking any action based on it, is strictly prohibited. > -----Original Message----- > From: James Melin [mailto:[EMAIL PROTECTED] > Sent: Friday, June 13, 2003 10:02 AM > To: [EMAIL PROTECTED] > Subject: Re: "invalidate: busy buffer" While Booting > > > Is there a way to convert to ext3 or reiserfs 'on the fly'? > Or do you have > to backup, reformat, restore? > > > |---------+----------------------------> > | | Jim Sibley | > | | <[EMAIL PROTECTED]| > | | com> | > | | Sent by: Linux on| > | | 390 Port | > | | <[EMAIL PROTECTED]| > | | IST.EDU> | > | | | > | | | > | | 06/12/2003 05:56 | > | | PM | > | | Please respond to| > | | Linux on 390 Port| > | | | > |---------+----------------------------> > > >------------------------------------------------------------- > -----------------------------------------------------------------| > | > | > | To: [EMAIL PROTECTED] > | > | cc: > | > | Subject: "invalidate: busy buffer" While Booting > | > > >------------------------------------------------------------- > -----------------------------------------------------------------| > > > > > "fsck.ext2: No such device or address while trying to open > /dev/VG01/homelv > " > > Long term solution - get off of ext2 as soon as possible and > move to ext3 > (redhat's preference) or reiser (SuSE's preference). When I > converted my > packs to one or the other, this problem virtually > disappeared, even in our > lab environment where systems are crashed for the fun of it. > > ext2 has no obligation to keep the meta data current and no > log to check if > its damaged. If a large, I/O intensive system crashes, you > data loss can be > big time with ext2. Also, under 64bit, an idle system with a > large memory > (5 or 6 GB) can have the same problem - who have thunk that > the root meta > data wouldn't be written out in a couple of days, so one of > our testers > reset the machine. Reult: ext2 damage to root and unable to IPL. > > Also, during IPL, the fsck is sufficiently slower than reiser > or ext3 that > it can extend the bring up time of a lot of Linux images when > your system > starts. > > Regards, Jim > Linux S/390-zSeries Support, SEEL, IBM Silicon Valley Labs > t/l 543-4021, 408-463-4021, [EMAIL PROTECTED] > *** Grace Happens *** >
