expanding root filesystem
gp...@gpuri.com
bid...@my-deja.com
filesystems or partitions short of reinstalling Solaris and specifying
new filesizes at that time. To save the data you will have to back it
up and restore later.
However the root filesystem is not something that should necessarily
fill up. You should analyze what is causing the filesystem to become
crowded and see if you can't move files, or compress your way out of
this problem.
Hope this helps,
Mike Cooper
In article <398C1582...@gpuri.com>,
gp...@gpuri.com wrote:
> How do you expand root filesystem without destroying the data ....
>
>
Sent via Deja.com http://www.deja.com/
Before you buy.
ho...@nospamextremejeep.com
> Unfortunately, I do not believe there is a way in Solaris of expanding
> filesystems or partitions short of reinstalling Solaris and specifying
> new filesizes at that time. To save the data you will have to back it
> up and restore later.
'man growfs' =) Though, you need to be using metadevices (via SDS, etc).
--
--
Hogan Whittall
__________________________________________________________________
This is formal notice under California Assembly Bill 1629, enacted
9/26/98 that any UCE sent to my email address will be billed $50
per incident to the legally allowed maximum of $25,000.
__________________________________________________________________
Karlheinz Kimmel
- Do you have Solstice Disk Suites (Formerly Online Disk Suites) installed:
you can do it with "growfs"
- Do you just have a standard Solaris system installed: you have to
repartition your disk where your root partition is located, this is not a
just simple operation...
- If you have Sun/Veritas Volume Manager installed: you can´t enlarge your
ufs root file system with running O/S, you also have to repartition your
file system sizes
Karlheinz Kimmel
<gp...@gpuri.com> schrieb im Newsbeitrag news:398C1582...@gpuri.com...
Andrew Gabriel
ho...@NOSPAMextremejeep.com writes:
>bid...@my-deja.com wrote:
>> Unfortunately, I do not believe there is a way in Solaris of expanding
>> filesystems or partitions short of reinstalling Solaris and specifying
>> new filesizes at that time. To save the data you will have to back it
>> up and restore later.
>
>'man growfs' =) Though, you need to be using metadevices (via SDS, etc).
If you can make the slice bigger (e.g. by freeing up the one afterwards
and merging it in with prtvtoc and fmthard, or format), then growfs
works fine without SDS. However, disksuite adds the ability to grow a
slice using non-contiguous disk space, using metadevices, which is
obviously more powerful and flexible.
--
Andrew Gabriel And...@cucumber.demon.co.uk
Consultant Software Engineer
bid...@my-deja.com
did not know about growfs because I have not yet touched Solaris 8 or
Solstice Disk Suite.
According to Sun's website, SDS comes standard with Solaris 8. It also
says it will work with Solaris 7 and 2.6 if you have Solaris Easy Access
Server Installed (software for connecting to an NT network). Neither
Solstice Disk Suite nor Easy Access Server appear to be a free download.
A shame, cause I would really like to play with it!
If your not currenly using Solaris 8, I would still say your best first
step is to make absolutely sure that you need to expand the partition.
If there is any way to solve the problem, by better distributing the
files on your system that would be the lesser of two headaches.
Philip Brown
>...
>If your not currenly using Solaris 8, I would still say your best first
>step is to make absolutely sure that you need to expand the partition.
>If there is any way to solve the problem, by better distributing the
>files on your system that would be the lesser of two headaches.
I conditionally disagree with that.
If you are talking bout redistributing things that belong on the root
filesystem, I would say dont do that.
On the other hand, splitting off /var is often a good idea.
Similarly, if there are non-sun-solaris directories, by all means move them
off to anotehr filesystem.
Otherwise, even f you dont have disksuite, you can use www.deja.com/usenet'
to search for old articles whih give you the syntax to mkfs or whatever.
"growfs" is just a wrapper for the underlying tool that is present on all
command solaris installs.
--
[Trim the no-bots from my address to reply to me by email!]
[ Do NOT email-CC me on posts. Pick one or the other.]
S.1618 http://thomas.loc.gov/cgi-bin/bdquery/z?d105:SN01618:@@@D
The word of the day is mispergitude
Roger Marquis
>- Do you have Solstice Disk Suites (Formerly Online Disk Suites) installed:
>you can do it with "growfs"
You not only need SDS installed but your also need to have previously
configured your root filesystem as a metadevice.
Even if that were the case you'd need to add metadevices that aren't
currently on the root disk creating an SDS boot dependency. This
is risky and not how root filesystems are typically configured.
The only root disk mirroring I'd recommend is RAID1 i.e. a straight
1 to 1 mirror to an identical hard drive. This will often allow
you to boot to one disk or the other even if SDS has problems.
Although the questioner doesn't specify, the source of his problem
is probably unnecessary partitioning of the root filesystem. Though
partitioning hasn't been necessary since 1 and 2GB drivers became
available (~1997) many admins still create partitions for /usr and
/var.
Unless you have a clear reason for creating root partitions they're
best avoided. If you need a larger /var/spool/mqueue or /var/spool/lp
for example, create those partitions on another disk and either
mount or symlink (ln -s) them to the original location. This will
save hours of maintenance over either root disk partitioning or
multi-disk root metadevices.
>- Do you just have a standard Solaris system installed: you have to
>repartition your disk where your root partition is located, this is not a
>just simple operation...
Repartitioning can be simple if you have a free disk available.
Just partition the spare disk (/ and swap), copy the existing root
filesystem over (ufsdump|ufsrestore;installboot), check the new
vfstab, and reboot to the new disk. Of course this may be more
difficult if it's your first time.
--
Roger Marquis
Roble Systems Consulting
http://www.roble.com/
Arthur Darren Dunham
Roger Marquis <not-fo...@roble.com> wrote:
>Karlheinz Kimmel <karlhein...@knuut.de> wrote:
>>- Do you have Solstice Disk Suites (Formerly Online Disk Suites) installed:
>>you can do it with "growfs"
>
>You not only need SDS installed but your also need to have previously
>configured your root filesystem as a metadevice.
Not necessarily true.
If there is "free space" on the disk past the end of the root partition,
you can use 'format' to extend the partition and then 'growfs' to
enlarge the filesystem.
You don't even *need* growfs. It's just a script that calls mkfs.
However calculating the figures to feed mkfs are tricky and running mkfs
on your root filesystem without knowing what you are doing is beyond
risky.
--
Darren Dunham ddu...@taos.com
Unix System Administrator Taos - The SysAdmin Company
Got some Dr Pepper? San Francisco Bay Area
< Please move on, ...nothing to see here, please disperse >
Ryan T. Tennant
being able to grow the root filesystem, I found it was not possible to grow the
root filesystem with growfs, makefs, newfs, or any other command while the
system was up. Note the bottom of the man page for exclusions to growfs. I
don't have a copy of disk suite loaded here at home, but the man page says
something to the effect of "You cannot grow the / or /usr filesystems. You can
also not grow /var (or any other volume) if accounting is turned on for that
volume, nor can you grow swap." Veritas Volume Manager and Disk Suite share
this limitation in not being able to grow the root volume. This is because
prior to growing the filesystem, it must lock it. See lockfs(1M).
It seems like the only way to do it is to boot from CD/net and grow it while the
filesystems are not mounted. I speculate here as that I have not yet had the
opportunity (or necessity) to try it.
Then again, I may be crazy thinking man pages are correct. Although my own
tests with growfs, mkfs, etc. showed them to be correct. Then again, I may have
missed something.
Take care.
Ryan Tennant
DevUnix.org