Sponsored Content
Operating Systems Solaris Need to attach one slice with existing concatenated volume Post 302592833 by bartus11 on Wednesday 25th of January 2012 04:36:45 AM
Old 01-25-2012
Yes, you can run it in production without unmounting the filesystem.
 

10 More Discussions You Might Find Interesting

1. Solaris

mirroring the boot slice (slice 8) on x86

Hi there I am about to mirror a Solaris 10 x86 box (SunFire X4100) onto a secondary disk using svm (current system is one disk). My question is this, on X86 boxes there is a slice 8 defined as boot partition (and also a slice 9, dunno what its used for tho). Do I need to mirror this boot slice... (0 Replies)
Discussion started by: hcclnoodles
0 Replies

2. Solaris

Disksuite Raid 0 Concatenated Volume - booting from cdrom

Hello, If I boot up from install media in single user mode (Solaris 9 - if it matters), will I be able to mount a concatenated volume? I have combined several disks into one non-os filesystem and I want to be able to mount it while booted in single user mode from cdrom. i.e., mount... (0 Replies)
Discussion started by: calmgreen
0 Replies

3. Solaris

Add existing user into an existing group

Pre: no gpasswd/adduser there is just usermod can be used, also there is no -a option for usermod. How should I add a user into a group? (4 Replies)
Discussion started by: a2156z
4 Replies

4. Shell Programming and Scripting

insert pipes for existing and non-existing records

I have a source file like this, L4058S462 34329094 F51010141TK1070000483L4058S462 34329094 0232384840 381892 182 5690 L4058S462 34329094 F51020141FIRST CLEARING, LLC A/C 3432-9094 L4058S462 34329094 F51030141JOHAN HOLMQVIST ... (1 Reply)
Discussion started by: saravanamr
1 Replies

5. UNIX for Dummies Questions & Answers

trying to devide existing physical volume

hi guys, i`m trying to take 40GB of my sda5 (/home mounted) to create new volume group(lvc) here`s the df output: /dev/sda2 7,9G 3,3G 4,3G 44% / udevfs 5,0M 60K 5,0M 2% /dev shmfs 379M 0 379M 0% /dev/shm tmpfs 379M ... (2 Replies)
Discussion started by: neverhood
2 Replies

6. UNIX for Dummies Questions & Answers

Confusion Regarding Physical Volume,Volume Group,Logical Volume,Physical partition

Hi, I am new to unix. I am working on Red Hat Linux and side by side on AIX also. After reading the concepts of Storage, I am now really confused regarding the terminologies 1)Physical Volume 2)Volume Group 3)Logical Volume 4)Physical Partition Please help me to understand these concepts. (6 Replies)
Discussion started by: kashifsd17
6 Replies

7. Solaris

Possible to increase swap size for existing UFS-based drive slice?

I like to increase swap size for my current server running solaris 10. Seems like the system is not using it's full 16G of physical memory. #swap -l swapfile dev swaplo blocks free /dev/dsk/c0t0d0s1 32,1 16 1058288 1058288 # swap -s total: 4125120k bytes... (17 Replies)
Discussion started by: JT-KGY
17 Replies

8. AIX

How to make existing volume group "shared"?

We have a 2 node cluster in which only the primary actually mounts the shared VGs at any specific time. We recently added a volume group to the primary. * The disks in it are visible to both nodes, but the secondary does not know about the new VG. * The new VG is not a "shared volume group" *... (10 Replies)
Discussion started by: ridgetop01
10 Replies

9. Red Hat

No space in volume group. How to create a file system using existing logical volume

Hello Guys, I want to create a file system dedicated for an application installation. But there is no space in volume group to create a new logical volume. There is enough space in other logical volume which is being mounted on /var. I know we can use that logical volume and create a virtual... (2 Replies)
Discussion started by: vamshigvk475
2 Replies

10. Solaris

Solaris 10 Volume Manager - adding slice to metadb

Hi all, I added a new disk slice to the current metadb. Below is what I see bash-3.2# metadb -i flags first blk block count a m p luo 16 8192 /dev/dsk/c0t0d0s7 a p luo 8208 8192 ... (3 Replies)
Discussion started by: javanoob
3 Replies
UMOUNT(8)						     Linux Programmer's Manual							 UMOUNT(8)

NAME
umount - unmount file systems SYNOPSIS
umount [-hV] umount -a [-dflnrv] [-t vfstype] [-O options] umount [-dflnrv] {dir|device}... DESCRIPTION
The umount command detaches the file system(s) mentioned from the file hierarchy. A file system is specified by giving the directory where it has been mounted. Giving the special device on which the file system lives may also work, but is obsolete, mainly because it will fail in case this device was mounted on more than one directory. Note that a file system cannot be unmounted when it is `busy' - for example, when there are open files on it, or when some process has its working directory there, or when a swap file on it is in use. The offending process could even be umount itself - it opens libc, and libc in its turn may open for example locale files. A lazy unmount avoids this problem. Options for the umount command: -V Print version and exit. -h Print help message and exit. -v Verbose mode. -n Unmount without writing in /etc/mtab. -r In case unmounting fails, try to remount read-only. -d In case the unmounted device was a loop device, also free this loop device. -i Don't call the /sbin/umount.<filesystem> helper even if it exists. By default /sbin/umount.<filesystem> helper is called if one exists. -a All of the file systems described in /etc/mtab are unmounted. (With umount version 2.7 and later: the proc filesystem is not unmounted.) -t vfstype Indicate that the actions should only be taken on file systems of the specified type. More than one type may be specified in a comma separated list. The list of file system types can be prefixed with no to specify the file system types on which no action should be taken. -O options Indicate that the actions should only be taken on file systems with the specified options in /etc/fstab. More than one option type may be specified in a comma separated list. Each option can be prefixed with no to specify options for which no action should be taken. -f Force unmount (in case of an unreachable NFS system). (Requires kernel 2.1.116 or later.) -l Lazy unmount. Detach the filesystem from the filesystem hierarchy now, and cleanup all references to the filesystem as soon as it is not busy anymore. (Requires kernel 2.4.11 or later.) --no-canonicalize Don't canonicalize paths. For more details about this option see the mount(8) man page. --fake Causes everything to be done except for the actual system call; this ``fakes'' unmounting the filesystem. It can be used to remove entries from /etc/mtab that were unmounted earlier with the -n option. THE LOOP DEVICE
The umount command will free the loop device (if any) associated with the mount, in case it finds the option `loop=...' in /etc/mtab, or when the -d option was given. Any pending loop devices can be freed using `losetup -d', see losetup(8). NOTES
The syntax of external umount helpers is: /sbin/umount.<suffix> {dir|device} [-nlfvr] [-t type.subtype] where the <suffix> is filesystem type or a value from "uhelper=" mtab option. The -t option is used for filesystems with subtypes support (for example /sbin/mount.fuse -t fuse.sshfs). The uhelper (unprivileged umount helper) is possible to used when non-root user wants to umount a mountpoint which is not defined in the /etc/fstab file (e.g devices mounted by HAL). FILES
/etc/mtab table of mounted file systems SEE ALSO
umount(2), mount(8), losetup(8). HISTORY
A umount command appeared in Version 6 AT&T UNIX. AVAILABILITY
The umount command is part of the util-linux package and is available from ftp://ftp.kernel.org/pub/linux/utils/util-linux/. Linux 2.0 26 July 1997 UMOUNT(8)
All times are GMT -4. The time now is 04:44 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy