> Actually my first live-and-learn experience with VVM was due to moving a > disk back and forth between servers (fast, easy and dangerous way to > move 4T of data);
Why dangerous? Deporting/importing disks to migrate data is a pretty normal thing. > the id's got mixed, VVM reported "already initialized" > for all new devices etc. so I experimentally mkfs'ed the real device > instead of vx device. Result: Disaster in a file system that consisted > of two concatenated disks. Deceivingly it worked fine for two weeks > until vxconfigd restarted probably upon VEA installation. "the id's got mixed" just shouldn't happen. I realize it's not part of your current issue, but I would be interested to understand more about what happened in this case. > Thus, I'm looking for a way to resize a file system without too much > hassle with temporary disks. You have chosen to set up your system in a way that few others appear to use: a diskgroup on a single LUN that you plan to resize. The FS and volume resize are trivial. Your issue is that dynamic lun resize appears to require multiple disks within the diskgroup to work. The only ways I know of around that issue are even more fiddly than using a temporary disk. (If you scripted it, the temp disk thing shouldn't be much of a hassle, but you would have to maintain it). -- Darren Dunham [EMAIL PROTECTED] 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
