Date: Fri, 06 Dec 2002 17:28:28 -0800 From: Kirk McKusick <mckusick@beastie.mckusick.com> To: Archie Cobbs <archie@dellroad.org> Cc: Julian Elischer <julian@elischer.org>, freebsd-current@FreeBSD.ORG, Thomas-Henning von Kamptz <tomsoft@FreeBSD.ORG> Subject: Re: backgroud fsck is still locking up system (fwd) Message-ID: <200212070128.gB71SS59094239@beastie.mckusick.com> In-Reply-To: Your message of "Fri, 06 Dec 2002 14:52:24 PST." <200212062252.gB6MqOhB066505@arch20m.dellroad.org>
next in thread | previous in thread | raw e-mail | index | archive | help
I suggest that we drag Thomas-Henning von Kamptz into this
discussion as he was one of the main authors of growfs. He
is copied on my reply.
Kirk McKusick
=-=-=-=-=-=
From: Archie Cobbs <archie@dellroad.org>
Subject: Re: backgroud fsck is still locking up system (fwd)
In-Reply-To: <Pine.BSF.4.21.0212061119170.45984-100000@InterJet.elischer.org>
To: Julian Elischer <julian@elischer.org>
Date: Fri, 6 Dec 2002 14:52:24 -0800 (PST)
CC: mckusick@beastie.mckusick.com, freebsd-current@FreeBSD.ORG
X-ASK-Info: Whitelist match
Julian Elischer wrote:
> most systems follow / with their swap region..
>
> you can boot from fixit, or picoBSD floppy
> and use disklabel -e to exend the root partition
> then you can use growfs to add the new space to your root fs.
Hmm.. I tried that and it didn't seem to work.
The disklabel change was successful, but growfs didn't seem to
expand the root partition any.. df(1) still shows it as 50M.
I ran growfs after booting single user mode but before mounting
any disks.. perhaps that caused it to not work.
Since that didn't work, I booted a 4.7-REL fixit floppy and tried
to run growfs from there, but then that growfs core dumped:
Program terminated with signal 11, Segmentation fault.
#0 0x804c089 in updclst (block=-874) at growfs.c:2335
2335 setbit(cg_clustersfree(&acg), block);
(gdb) list
2330 return;
2331 }
2332 /*
2333 * update cluster allocation map
2334 */
2335 setbit(cg_clustersfree(&acg), block);
2336
(gdb) where
#0 0x804c089 in updclst (block=-874) at growfs.c:2335
#1 0x8049584 in updjcg (cylno=2, utime=1039185218, fsi=4, fso=3, Nflag=0)
at growfs.c:862
#2 0x8048280 in growfs (fsi=4, fso=3, Nflag=0) at growfs.c:219
#3 0x804beb2 in main (argc=2, argv=0xbfbff7a4) at growfs.c:2213
#4 0x8048135 in _start ()
Notice "block=-874" which indicates something is weird or corrupted.
So now I've got extra space in the partition which (apparently) is
not being used and I can't seem to get at it (see below).
Plus I have a sneaking suspicion that I've screwed up something,
but there's nothing in the growfs man page that indicates what I
did was wrong.
FYI, this is a test machine so it's OK if it gets hosed.
-Archie
__________________________________________________________________________
Archie Cobbs * Packet Design * http://www.packetdesign.com
$ disklabel ad0s1
# /dev/ad0s1c:
type: ESDI
disk: ad0s1
label:
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 1860
sectors/unit: 29896902
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0
8 partitions:
# size offset fstype [fsize bsize bps/cpg]
a: 204800 0 4.2BSD 1024 8192 32768 # (Cyl. 0 - 12*)
b: 164608 204800 swap # (Cyl. 12*- 22*)
c: 29896902 0 unused 0 0 # (Cyl. 0 - 1860*)
e: 40960 369408 4.2BSD 1024 8192 16 # (Cyl. 22*- 25*)
f: 29486534 410368 4.2BSD 1024 8192 16 # (Cyl. 25*- 1860*)
$ df
Filesystem 1K-blocks Used Avail Capacity Mounted on
/dev/ad0s1a 49583 36751 8866 81% /
devfs 1 1 0 100% /dev
/dev/ad0s1f 14289643 2794938 10351534 21% /usr
/dev/ad0s1e 19815 3555 14675 20% /var
procfs 4 4 0 100% /proc
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200212070128.gB71SS59094239>