[prev in list] [next in list] [prev in thread] [next in thread] 

List:       veritas-vx
Subject:    Re: [Veritas-vx] VxFS 4.x and compatability with 3.x
From:       Darren Dunham <ddunham () taos ! com>
Date:       2005-07-29 17:27:41
Message-ID: 200507291727.KAA02122 () redwood ! taos ! com
[Download RAW message or body]

> I imported the disk group on our BCV without issue but when I ran fsck
> against the filesystem (necessary because we can't very well unmount a
> production filesystem, and never had to in the past) it didn't work.  Turns
> out the 4.x fsck can't utilize the 3.x filesystem intent log.  So, if you
> don't cleanly unmount your 3.x filesystem, you won't be able to use it in a
> 4.x environment unless you run a full fsck.  I ran the full fsck, it did its
> thing and I found files in lost+found, not exactly something reliable for
> backups.

Yeah, this came up on the list last year.

> Here's the technote detailing the issue:
> http://seer.support.veritas.com/docs/265504.htm
> <http://seer.support.veritas.com/docs/265504.htm> 
> 
> I'm just utterly astounded at the complete lack of foresight/vision on the
> part of Veritas regarding this issue.  This is going to be a pain in the ass
> to deal with and probably effect a lot of you.  So far the only workarounds
> we've come up with involve additional servers/resources to deal with it.

Could you make use of storage checkpoints?  That was mentioned as a
possible help.  It should be consistent.


-- 
Darren Dunham                                           ddunham@taos.com
Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >
_______________________________________________
Veritas-vx maillist  -  Veritas-vx@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-vx
[prev in list] [next in list] [prev in thread] [next in thread]