09-05-2010
I tried as 'newfs -m 1 \dev\rdsk\c0t1d0s0' but still the same error message.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Does anyone have a list of all the fstypes?
I don't know what fstype to use when mounting the cdrom...
Cheers;) (5 Replies)
Discussion started by: satan404
5 Replies
2. UNIX for Dummies Questions & Answers
Hello all
I'm new to this site and I have to say that ,it is just awesome. I was able to get most of my questions answered by reading the archives.
I've been a UNIX programmer for a while now but new to administration.
I just installed SunOS 5.9 on my desktop ( i86pc) . Everything... (3 Replies)
Discussion started by: luft
3 Replies
3. UNIX for Dummies Questions & Answers
Hi everyone,
I am a beginner in Linux and Shell scripting.I am migrating a couple of shell scripts from Solaris platform to Linux platform.In one script i saw a usage as :
/base/article/ocilib/lobfile $username/$password $filename $filepath
I didn't understand what this represents.The... (2 Replies)
Discussion started by: DILEEP410
2 Replies
4. Solaris
Hello,
I have a problem - I created a chrooted jail for one user. When I'm logged in as root, everything work fine, but when I'm logged in as a chrooted user - I have many problems:
1. When I execute the command ping, I get weird results:
bash-3.00$ usr/sbin/ping localhost ... (4 Replies)
Discussion started by: Przemek
4 Replies
5. UNIX for Advanced & Expert Users
Hi,
I have the following shell script :
Nbr_BD_Link=0
Nbr_BD_Link=`
sqlplus sysadm/${PSWD}@${DB_Name} << EOF | tail -4 | head -1 2>/dev/null
set head off feedback off ;
select count(*) from dba_db_links ;
exit ;
EOF `
echo ${Nbr_BD_Link}
if ; then
... (4 Replies)
Discussion started by: big123456
4 Replies
6. HP-UX
Hi, I am facing an issue with HP-UX box.
-bash-4.0$ uname -a
HP-UX ctsintco B.11.31 U ia64 2795347624 unlimited-user license
When ever iam doing a su - root, it is showing the below error
-bash-4.0$ su - root
Password:
su: Unknown id: root
Can you pls. let me know how to over come... (2 Replies)
Discussion started by: ysrikanth
2 Replies
7. AIX
Hi Guys,
I found on one of the server there are 2 VG's which I dont have any Idea of who created .. as below
bash-3.00$ lsvg
old_rootvg
rootvg
datavg
altinst_rootvg
altinst_rootvg under is meant for alternate disk installation.. But I'm not sure for which version of OS it was... (5 Replies)
Discussion started by: kkeng808
5 Replies
8. Linux
i am trying to build a simple rpm pacakage.
i am trying this example from this link
Creating the Spec File
i created rpm folder in my home directory of rpmbuild account.
in that i have sub folders BUILD,RPMS, SRPMS,SPECS ....
in SPECS folder i have a cdplayer spec file named... (1 Reply)
Discussion started by: anand121
1 Replies
9. Shell Programming and Scripting
Error mounting: mount exited with exit code 1: helper failed with:
mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or soThis happens when I try... (17 Replies)
Discussion started by: 1in10
17 Replies
10. Shell Programming and Scripting
Hello,
I am running ubuntu 16.04 .
Below script gives: "unknown command '\;'
counter=105
while read COL1 COL2 COL3
do
let counter++
url="http://localhost/test/$COL1.$COL2.$COL3";
mysql -uroot -D mydatabase -pmypasswd -e "SELECT video_id FROM video_series_files WHERE id IN \
(SELECT... (12 Replies)
Discussion started by: baris35
12 Replies
LEARN ABOUT DEBIAN
growfs.ufs
GROWFS(8) BSD System Manager's Manual GROWFS(8)
NAME
growfs -- grow size of an existing ufs file system
SYNOPSIS
growfs [-Ny] [-s size] special
DESCRIPTION
The growfs utility extends the newfs(8) program. Before starting growfs the disk must be labeled to a bigger size using bsdlabel(8). If you
wish to grow a file system beyond the boundary of the slice it resides in, you must re-size the slice using fdisk(8) before running growfs.
If you are using volumes you must enlarge them by using vinum(8). The growfs utility extends the size of the file system on the specified
special file. Currently growfs can only enlarge unmounted file systems. Do not try enlarging a mounted file system, your system may panic
and you will not be able to use the file system any longer. Most of the newfs(8) options cannot be changed by growfs. In fact, you can only
increase the size of the file system. Use tunefs(8) for other changes.
The following options are available:
-N ``Test mode''. Causes the new file system parameters to be printed out without actually enlarging the file system.
-y ``Expert mode''. Usually growfs will ask you if you took a backup of your data before and will do some tests whether special is cur-
rently mounted or whether there are any active snapshots on the file system specified. This will be suppressed. So use this option
with great care!
-s size
Determines the size of the file system after enlarging in sectors. This value defaults to the size of the raw partition specified in
special (in other words, growfs will enlarge the file system to the size of the entire partition).
EXAMPLES
growfs -s 4194304 /dev/vinum/testvol
will enlarge /dev/vinum/testvol up to 2GB if there is enough space in /dev/vinum/testvol.
SEE ALSO
bsdlabel(8), dumpfs(8), fdisk(8), ffsinfo(8), fsck(8), newfs(8), tunefs(8), vinum(8)
HISTORY
The growfs utility first appeared in FreeBSD 4.4.
AUTHORS
Christoph Herrmann <chm@FreeBSD.org>
Thomas-Henning von Kamptz <tomsoft@FreeBSD.org>
The GROWFS team <growfs@Tomsoft.COM>
BUGS
The growfs utility works starting with FreeBSD 3.x. There may be cases on FreeBSD 3.x only, when growfs does not recognize properly whether
or not the file system is mounted and exits with an error message. Then please use growfs -y if you are sure that the file system is not
mounted. It is also recommended to always use fsck(8) after enlarging (just to be on the safe side).
For enlarging beyond certain limits, it is essential to have some free blocks available in the first cylinder group. If that space is not
available in the first cylinder group, a critical data structure has to be relocated into one of the new available cylinder groups. On
FreeBSD 3.x this will cause problems with fsck(8) afterwards. So fsck(8) needs to be patched if you want to use growfs for FreeBSD 3.x.
This patch is already integrated in FreeBSD starting with FreeBSD 4.4. To avoid an unexpected relocation of that structure it is possible to
use ffsinfo -g 0 -l 4 on the first cylinder group to verify that nbfree in the CYLINDER SUMMARY (internal cs) of the CYLINDER GROUP cgr0 has
enough blocks. As a rule of thumb for default file system parameters one block is needed for every 2 GB of total file system size.
Normally growfs writes this critical structure to disk and reads it again later for doing more updates. This read operation will provide
unexpected data when using -N. Therefore, this part cannot really be simulated and will be skipped in test mode.
BSD
September 8, 2000 BSD