Re: Error writing ufs log state problem

From: Beardy (beardy_at_beardy.net)
Date: 09/24/04 

Date: Fri, 24 Sep 2004 17:48:40 +0000

Keg wrote:
> Beardy <beardy@beardy.net> wrote in message news:<41534cd1$0$42247$ed2e19e4@ptn-nntp-reader04.plus.net>...
>
>>Keg wrote:
>>
>>>I am getting this error during boot of a Solaris 9 64-bit system.
>>>
>>>...
>>>jnic146x1: Target9: Lun28 supported.
>>>jnic146x1: Target9: Lun29 supported.
>>>jnic146x1: Target9: Lun30 supported.
>>>jnic146x1: Target9: Lun31 supported.
>>>WARNING: Error writing ufs log state
>>>WARNING: ufs log for / changed state to Error
>>>WARNING: Please umount(1M) / and run fsck(1M)
>>>Starting VxVM restore daemon...
>>>VxVM starting in boot mode...
>>>...
>>>
>>>I am remotely managing this machine so I can't boot from CD at the
>>>moment to fsck the root filesystem. Is this something critical or
>>>something I can fix w/o booting from a CD?
>>>
>>>Thx,
>>>rhugga
>>
>>I have had this once, and was left with a read-only root filesystem. My,
>>and I suspect, your only solution is to boot single-user from CD :-(
>>Depending on your filesystem structure, the system might continue to run
>>to some extent - only you can determine that.
>>
>>But if the system panics, and you have a bad log area for root, I
>>suspect that you *will* be paying a visit ;-)
>>
>>Apols for being no help. Hopefully other people in this NG will have
>>better ideas.
>>
>>
>>Beardy.
>
>
>
> Actually I ended up booting from CD an fsck'ing the filesystem several
> times and I still get that error on boot. When I performed the fsck's,
> it found no problems as all. I ran fsck 3 times.
>
> Any ideas anoyone,
> thx,
> rhugga

Do you have a Veritas encapsulated root filesystem? What device are you
fsck'ing? I suspect that Veritas is getting in the way somehow, and
although I am not a Veritas expert at all, there are many who contribute
here.

Relevant Pages

  • Re: Read-only root (/) except /et
    ... in other words, again root is compromised. ... That means that in a standard config the root filesystem cannot be made ... backup, and fewer writes means less likelihood of corruption eg if power ... Note that all my live partitions are rsync'd with identical ...
    (Debian-User)
  • Re: Read-only root (/) except /et
    ... in other words, again root is compromised. ... That means that in a standard config the root filesystem cannot be made ... backup, and fewer writes means less likelihood of corruption eg if power ... Note that all my live partitions are rsync'd with identical ...
    (Debian-User)
  • Re: UFS Bug: FreeBSD 6.1/6.2/7.0: MOKB-08-11-2006, CVE-2006-5824, MOKB-03
    ... They can simply mount a filesystem with any number of SUID ... root binaries on it and have their way with the box. ... I don't think anyone is arguing whether or not this is a bug. ...
    (FreeBSD-Security)
  • Re: Disk Druid - Fedora flame #1
    ... What I do as root, ... Root's home directory should contain very little: ... part of a minimal boot environment. ... And the root filesystem should be as small as reasonably possible, ...
    (Fedora)
  • Re: Disk Druid - Fedora flame #1
    ... >Gene Heskett wrote: ... > be part of a minimal boot environment. ... >And the root filesystem should be as small as reasonably possible, ... as long as root is trusted. ...
    (Fedora)