Long story short, we are trying to utilize block based backups for some 30 million files on a 2 node A/P VCS. Product will not support vxfs, and one of our ideas was to simply keep the vxvm pieces so the scripting and VCS controls all work the same, but simply make the FSs as ext4. I've tried every combination of mkfs and mke2fs commands against a fresh DG and volume, but it never can do it:
mke4fs -F /dev/vx/rdsk/RestoreTarget/RestoreVol2
mke4fs 1.41.12 (17-May-2010)
Warning: could not erase sector 2: Attempt to write block from filesystem resulted in short write
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
67108864 inodes, 268435456 blocks
13421772 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=4294967296
8192 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
Warning: could not erase sector 0: Attempt to write block from filesystem resulted in short write
mke4fs: Attempt to write block from filesystem resulted in short write while zeroing block 268435440 at end of filesystem
Writing inode tables: 0/8192
Could not write 7 blocks in inode table starting at 1057: Attempt to write block from filesystem resulted in short write
Regardless of the options used, it appears this won't work, so my first question is "should it" and the other is, is there any downside to having VCS managing failover of native LVM/ext4 FS's if this theory cannot pan out?
RHEL5.10, VXSF 5.1+
thanks