Sponsored Content
Full Discussion: Resizing the Root Filesystem
Operating Systems Solaris Resizing the Root Filesystem Post 302418071 by gowthamakanthan on Monday 3rd of May 2010 12:53:16 AM
Old 05-03-2010
Without reboot is not possible ??
 

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

/root filesystem size is full

hi in my server ( / ) root filesystem size is full how to reduce the size and what are the files i want to remove. i need answer for linux and AIX also. (6 Replies)
Discussion started by: chomca
6 Replies

3. Solaris

Move root filesystem to other slice

Hi, df -h display: # 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%... (4 Replies)
Discussion started by: lamoul
4 Replies

4. Solaris

Root Filesystem

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

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

6. Linux

Encrypt already install root filesystem

All, Is there a way to encrypt my Ubuntu root HD after installation? (1 Reply)
Discussion started by: markdjones82
1 Replies

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

8. Red Hat

Resizing root virtual disk on the CentOS

Hello, Can someone suggest me what I missing, I re-sized a root virtual disk to 30GB on the CentOS VM. After re-sizing the disk, I booted the OS and ran fdisk -list command I was able view the size of the disk as 30GB. Paritions in the vm before I resize are: /boot - Primary parition /... (1 Reply)
Discussion started by: bobby320
1 Replies

9. Red Hat

How to resize filesystem by resizing the LUN without impact to applications.?

Is it possible to resize a filesystem by resizing the LUN on RHEL 6.4 64-bit with LVM and no impact to running applications? The research I have done so far seems to take the approach of adding a new LUN and then expaning the volume group to the new LUN. I'm looking for an approach that avoids a... (7 Replies)
Discussion started by: aenagy
7 Replies
Sys::Filesystem::Linux(3pm)				User Contributed Perl Documentation			       Sys::Filesystem::Linux(3pm)

NAME
Sys::Filesystem::Linux - Return Linux filesystem information to Sys::Filesystem SYNOPSIS
See Sys::Filesystem. INHERITANCE
Sys::Filesystem::Linux ISA Sys::Filesystem::Unix ISA UNIVERSAL METHODS
version () Return the version of the (sub)module. ATTRIBUTES
The following is a list of filesystem properties which may be queried as methods through the parent Sys::Filesystem object. fs_spec Dscribes the block special device or remote filesystem to be mounted. For ordinary mounts it will hold (a link to) a block special device node (as created by mknod(8)) for the device to be mounted, like /dev/cdromaXX or aXX/dev/sdb7aXX. For NFS mounts one will have <host>:<dir>, e.g., aXXknuth.aeb.nl:/aXX. For procfs, use aXXprocaXX. Instead of giving the device explicitly, one may indicate the (ext2 or xfs) filesystem that is to be mounted by its UUID or volume label (cf. e2label(8) or xfs_admin(8)), writing LABEL=<label> or UUID=<uuid>, e.g., aXXLABEL=BootaXX or aXXUUID=3e6be9de-8139-11d1-9106-a43f08d823a6aXX. This will make the system more robust: adding or removing a SCSI disk changes the disk device name but not the filesystem volume label. fs_file Describes the mount point for the filesystem. For swap partitions, this field should be specified asaXXnone. If the name of the mount point contains spaces these can be escaped asaXX40. fs_vfstype Dscribes the type of the filesystem. Linux supports lots of filesystem types, such as adfs, affs, autofs, coda, coherent, cramfs, devpts, efs, ext2, ext3, hfs, hpfs, iso9660, jfs, minix, msdos, ncpfs, nfs, ntfs, proc, qnx4, reiserfs, romfs, smbfs, sysv, tmpfs, udf, ufs, umsdos, vfat, xenix, xfs, and possibly others. For more details, see mount(8). For the filesystems currently supported by the running kernel, see /proc/filesystems. An entry swap denotes a file or partition to be used for swapping, cf. swapon(8). An entry ignore causes the line to be ignored. This is useful to show disk partitions which are currently unused. fs_mntops Describes the mount options associated with the filesystem. It is formatted as a comma separated list of options. It contains at least the type of mount plus any additional options appropriate to the filesystem type. For documentation on the available options for non- nfs file systems, see mount(8). For documentation on all nfs-specific options have a look at nfs(5). Common for all types of file system are the options aXXaXXnoautoaXXaXX (do not mount when 'mount -a' is given, e.g., at boot time), aXXaXXuseraXXaXX (allow a user to mount), and aXXaXXowneraXXaXX (allow device owner to mount), and aXXaXX_netdevaXXaXX (device requires network to be available). The aXXaXXowneraXXaXX and aXXaXX_netdevaXXaXX options are Linux-specific. For more details, see mount(8). fs_freq Used for these filesystems by the dump(8) command to determine which filesystems need to be dumped. If the fifth field is not present, a value of zero is returned and dump will assume that the filesystem does not need to be dumped. fs_passno Used by the fsck(8) program to determine the order in which filesystem checks are done at reboot time. The root filesystem should be specified with a fs_passno of 1, and other filesystems should have a fs_passno of 2. Filesystems within a drive will be checked sequentially, but filesystems on different drives will be checked at the same time to utilize parallelism available in the hardware. If the sixth field is not present or zero, a value of zero is returned and fsck will assume that the filesystem does not need to be checked. SEE ALSO
Sys::Filesystem, Sys::Filesystem::Unix, fstab(5) VERSION
$Id: Linux.pm 128 2010-05-12 13:16:44Z trevor $ AUTHOR
Nicola Worthington <nicolaw@cpan.org> - <http://perlgirl.org.uk> Jens Rehsack <rehsack@cpan.org> - <http://www.rehsack.de/> COPYRIGHT
Copyright 2004,2005,2006 Nicola Worthington. Copyright 2009,2010 Jens Rehsack. This software is licensed under The Apache Software License, Version 2.0. <http://www.apache.org/licenses/LICENSE-2.0> perl v5.10.1 2010-05-18 Sys::Filesystem::Linux(3pm)
All times are GMT -4. The time now is 07:59 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy