Sponsored Content
Operating Systems Solaris Move root filesystem to other slice Post 302277094 by lamoul on Thursday 15th of January 2009 11:35:30 AM
Old 01-15-2009
Move root filesystem to other slice

Hi,

df -h display:
Code:
# df -h
Filesystem size used avail capacity Mounted on
/dev/dsk/c1t0d0s0 9.8G 8.1G 1.7G 84% /
/proc 0K 0K 0K 0% /proc
mnttab 0K 0K 0K 0% /etc/mnttab
fd 0K 0K 0K 0% /dev/fd
swap 1.0G 152K 1.0G 1% /var/run
swap 1.1G 24M 1.0G 3% /tmp
/dev/dsk/c1t0d0s3 57G 13G 43G 24% /adv1

I'd like to copy Os on /dev/dsk/c1t0d0s3 this slice has 43G free space but try to
1) mkdir /filesystemcopy
2) mount /dev/dsk/c1t0d0s3 but it complaining that: # mkdir /filesystemtest
# mount /dev/dsk/c1t0d0s3 /filesystemtest
mount: /dev/dsk/c1t0d0s3 is already mounted, /filesystemtest is busy,
or the allowable number of mount points has been exceeded
/avd1 is live database and application.

Could someone help please?

Thanks

Last edited by lamoul; 01-15-2009 at 01:32 PM.. Reason: How to copy filesystem on another slice on Solaris 5.9
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Mounted Root Filesystem

In my Solaris 10 based server, I have noticed the following mounts when a use DF -K /dev/dsk/c0t0d0s0 5062414 3213876 1797914 65% / / 5062414 3213876 1797914 65% /net/se420 I understand the first mount because it appears in my vfstab file and is the mount of root that I would expect.... (1 Reply)
Discussion started by: jimthompson
1 Replies

2. 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

3. UNIX for Dummies Questions & Answers

Move veritas filesystem space between Logical volumes

I have a veritas file system (fsA) that is nearing capacity. We have secondary file system (fsB). that is unused and would like to move some of it's disk space but I'm unsure as to how to do this with. /dev/vx/dsk/vg05/lvol05 25288704 21887258 3188911 88% ... (2 Replies)
Discussion started by: Steelysteel
2 Replies

4. Solaris

Ways to analyse root disk slice

Hi, Recently I faced with need of analyze root disk. I figured out two possible ways to do it: 1. Practical. Boot from CD and run format 2. Theoretical. Create live upgrade boot environment on another disk, activate it, reboot, unmont all root disk partitions and run format. I've already... (3 Replies)
Discussion started by: Sapfeer
3 Replies

5. Solaris

Root Filesystem

Hi, Can we install root file system on other than 0th slice???? (5 Replies)
Discussion started by: tirupathiraju_t
5 Replies

6. UNIX for Dummies Questions & Answers

Root filesystem filling up!

Hi all. New to the forum and new to Unix admin... / filesystem filled up and I can't find where the large files are. Any help will be apppreciated: # df -k Filesystem kbytes used avail capacity Mounted on /dev/dsk/c1t0d0s0 8063580 7941745 41200 100% / /proc ... (4 Replies)
Discussion started by: jamie_collins
4 Replies

7. Solaris

Resizing the Root Filesystem

Is it possible to increase the root filesystem size without reboot ?? (4 Replies)
Discussion started by: gowthamakanthan
4 Replies

8. UNIX for Dummies Questions & Answers

Solaris 2.6 - Duplicate Filesystem to a larger slice(same drive)

One of our production systems has a slice called "oldslice" that periodically runs low on space during normal operation. We have minimum requirements for online data retention, and whoever sized this slice didn't give it much wiggle room, so it periodically runs low on space. I'm getting tired of... (1 Reply)
Discussion started by: the.gooch
1 Replies

9. Linux

root filesystem goes readonly

I see this when tried to create a dir using root fstab entries are pretty normal tried to remount with rw but it is still the same block device /dev/sda2 is write-protected ---------- Post updated at 04:57 PM ---------- Previous update was at 03:51 PM ---------- fstab entry ... (4 Replies)
Discussion started by: robo
4 Replies
growfs(1M)						  System Administration Commands						growfs(1M)

NAME
growfs - non-destructively expand a UFS file system SYNOPSIS
/usr/sbin/growfs [-M mount-point] [newfs-options] [raw-device] DESCRIPTION
growfs non-destructively expands a mounted or unmounted UNIX file system (UFS) to the size of the file system's slice(s). Typically, disk space is expanded by first adding a slice to a metadevice, then running the growfs command. When adding space to a mirror, you expand each submirror before expanding the file system. growfs will ``write-lock'' (see lockfs(1M)) a mounted file system when expanding. The length of time the file system is write-locked can be shortened by expanding the file system in stages. For instance, to expand a 1 Gbyte file system to 2 Gbytes, the file system can be grown in 16 Mbyte stages using the -s option to specify the total size of the new file system at each stage. The argument for -s is the number of sectors, and must be a multiple of the cylinder size. Note: The file system cannot be grown if a cylinder size of less than 2 is specified. Refer to the newfs(1M) man page for information on the options available when growing a file system. growfs displays the same information as mkfs during the expansion of the file system. If growfs is aborted, recover any lost free space by unmounting the file system and running the fsck command, or run the growfs command again. OPTIONS
Root privileges are required for all of the following options. -M mount-point The file system to be expanded is mounted on mount-point. File system locking (lockfs) will be used. newfs-options The options are documented in the newfs man page. raw-device Specifies the name of a raw metadevice or raw special device, residing in /dev/md/rdsk, or /dev/rdsk, respectively, including the disk slice, where you want the file system to be grown. EXAMPLES
Example 1 Expanding nonmetadevice slice for /export file system The following example expands a nonmetadevice slice for the /export file system. In this example, the existing slice, /dev/dsk/c1t0d0s3, is converted to a metadevice so additional slices can be concatenated. # metainit -f d8 2 1 c1t0d0s3 1 c2t0d0s3 # umount /export Example 2 Associate /export with new metadevice Edit the /etc/vfstab file to change the entry for /export to the newly defined metadevice, d8. # mount /export # growfs -M /export /dev/md/rdsk/d8 The first example starts by running the metainit command with the -f option to force the creation of a new concatenated metadevice d8, which consists of the existing slice /dev/dsk/c1t0d0s3 and a new slice /dev/dsk/c2t0d0s3. Next, the file system on /export must be unmounted. The /etc/vfstab file is edited to change the entry for /export to the newly defined metadevice name, rather than the slice name. After the file system is remounted, the growfs command is run to expand the file system. The file system will span the entire metadevice when growfs completes. The -M option enables the growfs command to expand a mounted file system. During the expansion, write access for /export is suspended until growfs unlocks the file system. Read access is not affected, though access times are not kept when the lock is in effect. Example 3 Dynamic Expansion of /export file system The following example picks up from the previous one. Here, the /export file system mounted on metadevice d8 is dynamically expanded. # metattach d8 c0t1d0s2 # growfs -M /export /dev/md/rdsk/d8 This example begins by using the metattach command to dynamically concatenate a new slice, /dev/dsk/c0t1d0s2, to the end of an existing metadevice, d8. Next, the growfs command specifies that the mount-point is /export and that it is to be expanded onto the raw metadevice /dev/md/rdsk/d8. The file system will span the entire metadevice when growfs completes. During the expansion, write access for /export is suspended until growfs unlocks the file system. Read access is not affected, though access times are not kept when the lock is in effect. Example 4 Expanding mounted file system to existing mirror The following example expands a mounted file system /files, to an existing mirror, d80, which contains two submirrors, d9 and d10. # metattach d9 c0t2d0s5 # metattach d10 c0t3d0s5 # growfs -M /files /dev/md/rdsk/d80 In this example, the metattach command dynamically concatenates the new slices to each submirror. The metattach command must be run for each submirror. The mirror will automatically grow when the last submirror is dynamically concatenated. The mirror will grow to the size of the smallest submirror. The growfs command then expands the file system. The growfs command specifies that the mount-point is /files and that it is to be expanded onto the raw metadevice /dev/md/rdsk/d80. The file system will span the entire mirror when the growfs command completes. During the expansion, write access for the file system is suspended until growfs unlocks the file system. Read access is not affected, though access times are not kept when the lock is in effect. EXIT STATUS
The following exit values are returned: 0 Successful completion. >0 An error occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWmdu | +-----------------------------+-----------------------------+ SEE ALSO
fsck(1M), lockfs(1M), mkfs(1M), metattach(1M), newfs(1M), attributes(5) Solaris Volume Manager Administration Guide LIMITATIONS
Only UFS file systems (either mounted or unmounted) can be expanded using the growfs command. Once a file system is expanded, it cannot be decreased in size. The following conditions prevent you from expanding file systems: When acct is activated and the accounting file is on the target device. When C2 security is activated and the logging file is on the target file system. When there is a local swap file in the target file system. When the file system is root (/), /usr, or swap. SunOS 5.11 9 Dec 2003 growfs(1M)
All times are GMT -4. The time now is 03:09 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy