In the last episode (Jan 16), The-IRC FreeBSD said:
> I am sorry if I am asking a question that might have been brought up
> before I have attempted to research my issue but it has many angles it
> might be listed under so please bare with me.
>
> We have had ongoing problems with UFS Errors on our root partition (and
> any additional partition that did not have soft-updates enabled by
> default) and we recently had a problem with a secondary drive that housed
> home directories completely filled up and then everything locked up due-to
> huge CPU and Memory usage because nothing was able to write to the drive
> but when the server was rebooted it failed to bootup because of critical
> errors on the root partition.
>
> We have /etc and /usr on the root partition and our home/var partitions
> mistakenly do not have soft-updates flag set.
>
> ::dmesg::
> http://the-irc.com/dmesg
>
> ::mount::
> /dev/ad4s1a on / (ufs, local)
> devfs on /dev (devfs, local, multilabel)
> /dev/ad4s1d on /home (ufs, local, with quotas)
> /dev/ad4s1e on /tmp (ufs, local, noexec, nosuid, soft-updates)
> /dev/ad4s1f on /var (ufs, local)
> devfs on /var/named/dev (devfs, local, multilabel)
> procfs on /proc (procfs, local)
> /dev/ad0s1e on /Backups (ufs, local, soft-updates)
> /dev/ad0s1d on /root (ufs, local, soft-updates)
>
> ::fsck /::
> ** /dev/ad4s1a (NO WRITE)
fsck'ing a filesystem that is currently mounted read-write will always
produce errors. Boot in single-user mode if you want to check the root
filesystem or other fs'es that you can't dismount in multi-user mode.
--
Dan Nelson
dnel...@allantgroup.com
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
