Date: Thu, 14 Jul 2005 16:17:06 -0400 From: asym <bsdlists@rfnj.org> To: freebsd-stable@freebsd.org, freebsd-questions@freebsd.org Subject: Re: dangerous situation with shutdown process Message-ID: <6.2.1.2.2.20050714161537.0378c310@mail.rfnj.org> In-Reply-To: <20050714191942.GA98637@freebie.xs4all.nl> References: <42D6B117.5080302@plab.ku.dk> <20050714191449.A8A615D07@ptavv.es.net> <20050714191942.GA98637@freebie.xs4all.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
At 15:19 7/14/2005, Wilko Bulte wrote: >On Thu, Jul 14, 2005 at 12:14:49PM -0700, Kevin Oberman wrote.. > > > Date: Thu, 14 Jul 2005 20:38:15 +0200 > > > From: Anatoliy Dmytriyev <tolid@plab.ku.dk> > > > Sender: owner-freebsd-stable@freebsd.org > > > > > > Hello, everybody! > > > > > > I have found unusual and dangerous situation with shutdown process: > > > I did a copy of 200 GB data on the 870 GB partition (softupdates is > > > enabled) by cp command. > > > It took a lot of time when I did umount for this partition exactly= after > > > cp, but procedure finished correctly. > > > In case, if I did =E2=80=9Cshutdown =E2=80=93h(r)=E2=80=9D, also= exactly after cp, the=20 > shutdown > > > procedure waited for =E2=80=9Csync=E2=80=9D (umounting of the file= system) but sync > > > process was terminated by timeout, and fsck checked and did= correction > > > of the file system after boot. > > > > > > System 5.4-stable, RAM 4GB, processor P-IV 3GHz. > > > > > > How can I fix it on my system? The funny thing about all the replies here.. is that this guy is not saying= =20 that sync doesn't work. He's saying that the timeout built into shutdown causes it to *terminate*=20 the sync forcibly before it's done, and then reboot. All finger pointing about IDE, SCSI, softupdates, and journals aside.. I=20 think all he wants/needs is a way to increase that timer.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.2.1.2.2.20050714161537.0378c310>