Re: Solaris 8, VxVM 3.1 and vxresize

From: Darren Dunham (ddunham_at_redwood.taos.com)
Date: 02/02/04 

Date: Mon, 02 Feb 2004 22:20:51 GMT

pfalpha <pfalpha@nospamfores.plus.com> wrote:
> I note various issues with extending a mirrored UFS volume with
"logging" switched on. The VxVM version is 3.1 with patch Solaris 8
110283-05 applied.

You're saying that you've read about the issues or that they've happened
to you? What exactly were the "various issues"? Did you get explicit
errors from the mkfs/growfs, or did it appear to succeed but give
strange behavior?

> Basically issues occur if :
>
> 1) the filesystem has logging switched on.
> 2) the filesystem is greater than 8Gb
> 3) the extension is greater than an additional 8Gb
>
> All of which is true in my case.
>
> The questions are..
> 1) has the patch fixed the problem, as I don't have a test rig to
> pre-test.

I can't tell from the descriptions if any particular update of this
patch exactly addresses your situation.

> 2) When to use vxresize over vxassist "growby".

This I can answer.

'vxassist' is always a volume level instruction. This will only change
the size of the volume and will not touch the filesystem contained
within. If you do a 'vxassist growby', you'll need to run either
'growfs' or a more manual 'mkfs' to enlarge the filesystem.

'vxresize' is a program that attempts to do both operations in a single
program. It will first enlarge the container, then attempt to determine
the filesystem in use, then enlarge the filesystem. 

-- 
Darren Dunham                                           ddunham@taos.com
Unix System Administrator                    Taos - The SysAdmin Company
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

Relevant Pages

  • Re: [Ext2-devel] [PATCH 1/2] ext2/3: Support 2^32-1 blocks(Kernel)
    ... point out that's a seperate issue- that's for enlarge the file size, ... for expand the max filesystem size. ... I'll remove them when I update the patch next time. ... like extents, but even extents still need to allow a larger i_blocks, ...
    (Linux-Kernel)
  • [PATCH 2.6.0-test5 latest bk]mqueue filesystem
    ... changes in 2.6.0-test4 caused your patch to no longer build. ... I have been hammering the hell out of this filesystem ... POSIX message queues fs ... +static int proc_write_max_queues(struct file *file, ...
    (Linux-Kernel)
  • [PATCH 0/4] jbd: possible filesystem corruption fixes (rebased)
    ... Subject: jbd: possible filesystem corruption fixes (rebased) ... This patch set fixes several error handling problems. ...
    (Linux-Kernel)
  • Re: [PATCH] lockfs patch for 2.6
    ... Christoph's vfs patch looks good, I've stripped out the XFS bits (FS ... I had to add a struct super_block pointer to ... * block device, we hould a read lock on the s->s_umount sem to make sure ... Lock the filesystem while a device is suspended. ...
    (Linux-Kernel)
  • Re: [PATCH] Add notification of page becoming writable to VMA ops
    ... >> The attached patch adds a new VMA operation to notify a filesystem or other ... that reduces the size of the patch. ... Linux NTFS maintainer / IRC: ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)