xfs
[Top] [All Lists]

Re: [Evms-devel] Re: "Invalid client ID" after system lockup and subsequ

To: Seth Mos <knuffie@xxxxxxxxx>
Subject: Re: [Evms-devel] Re: "Invalid client ID" after system lockup and subsequent reset ?
From: karlheg@xxxxxxxxxxxx (Karl M. Hegbloom)
Date: 29 Jul 2002 22:24:49 -0700
Cc: Stephen Lord <lord@xxxxxxx>, XFS <linux-xfs@xxxxxxxxxxx>, EVMS Devel <evms-devel@xxxxxxxxxxxxxxxxxxxxx>
In-reply-to: <20020728004219.K60206-100000@xs1.xs4all.nl>
References: <20020728004219.K60206-100000@xs1.xs4all.nl>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Honest Recruiter)
Seth Mos <knuffie@xxxxxxxxx> writes:

> On 27 Jul 2002, Karl M. Hegbloom wrote:
> 
> > Seth Mos <knuffie@xxxxxxxxx> writes:
> >
> > > Clearing the log was enough to make it mount again.  I saw this
> > > about 3 times. After upgrading to a later kernel I never saw the
> > > problem again. The problem was no present with earlier kernels
> > > either.
> >
> > Do you use EVMS?
> 
> No but the issue was that playing back recovery from the low was
> hanging.  If I understand correctly EVMS is a layer underneath the
> filessytem and this could mean that there is something in the log
> which the recovery code has a tough time with.

Wrong; that's just one result of the real problem that I reported.
(Please go back and read my report again)

I'm complaining that when I compile large software systems, and
there's a lot of disk activity, my computer locks up.  It behaves,
IMO, as though there is a deadlock in the file system code.  Programs
that are already running keep going, but I cannot launch new ones or
do anything that requires access to the filesystem.  I have no
recourse but to press the reset button, and at reboot, the log replay
error happens.  No wonder; it cannot write the log entry and then gets
interrupted by a hardware reset while it's waiting for the deadlock to
end?

I wonder if it's an SMP + XFS + EVMS (or any combination involving
SMP) issue, so I wrote to these lists to see if anyone knows what's
the matter.

It occurs to me that you may need more information...  I'm running a
Debian 2.4.18 kernel image with (can I get the XFS and EVMS version
numbers from the running kernel somehow?  If not, please make that
possible... Ah, yes, dmesg... Alright, Mr. XFS?  Will you PLEASE make
it print a version number at boot?) patches supplied by Debian
packages.  IIRC, it was more than two months ago that I built the
kernel I am running now, which displays the buggy behavior.  (The last
try with fresh patches would not boot due to the unaligned access
bug you already know about.)

The machine was originally configured with LVM, then I switched to
EVMS.

evms: EVMS v1.0.1 initializing .... info level(5).
evms: object detected, deleting 'lvm/bittersweet/snapshot_area'.
evms: Exporting EVMS Volume(63,255) from "/dev/evms/quota_tests".
evms: Exporting EVMS Volume(63,254) from "/dev/evms/mirror".
evms: Exporting EVMS Volume(63,253) from "/dev/evms/opt".
evms: Exporting EVMS Volume(63,1) from "/dev/evms/hdg1".
evms: Exporting EVMS Volume(63,2) from "/dev/evms/hde1".
evms: Exporting EVMS Volume(63,3) from "/dev/evms/hda1".
evms: Exporting EVMS Volume(63,4) from "/dev/evms/hda2".
evms: Exporting EVMS Volume(63,5) from "/dev/evms/lvm/bittersweet/slash".
evms: Exporting EVMS Volume(63,6) from "/dev/evms/lvm/bittersweet/home".
evms: Exporting EVMS Volume(63,7) from "/dev/evms/lvm/bittersweet/src".
evms: Exporting EVMS Volume(63,8) from "/dev/evms/lvm/bittersweet/usr_local".
evms: Exporting EVMS Volume(63,9) from "/dev/evms/lvm/bittersweet/var".
evms: Exporting EVMS Volume(63,10) from "/dev/evms/lvm/bittersweet/usr".

SGI XFS with ACLs, DMAPI, realtime, quota, no debug enabled
...
XFS mounting filesystem ide0(3,1)
XFS: WARNING: recovery required on readonly filesystem.
XFS: write access will be enabled during mount.
Starting XFS recovery on filesystem: ide0(3,1) (dev: 3/1)
hub.c: USB new device connect on bus1/2, assigned device number 3
Ending XFS recovery on filesystem: ide0(3,1) (dev: 3/1)
VFS: Mounted root (xfs filesystem) readonly.
...
XFS mounting filesystem evms(63,10)
Starting XFS recovery on filesystem: evms(63,10) (dev: 63/10)
Ending XFS recovery on filesystem: evms(63,10) (dev: 63/10)
XFS mounting filesystem evms(63,9)
Starting XFS recovery on filesystem: evms(63,9) (dev: 63/9)
Ending XFS recovery on filesystem: evms(63,9) (dev: 63/9)
XFS mounting filesystem evms(63,8)
XFS mounting filesystem evms(63,7)
Starting XFS recovery on filesystem: evms(63,7) (dev: 63/7)
Ending XFS recovery on filesystem: evms(63,7) (dev: 63/7)
XFS mounting filesystem evms(63,6)
Starting XFS recovery on filesystem: evms(63,6) (dev: 63/6)
Ending XFS recovery on filesystem: evms(63,6) (dev: 63/6)
XFS mounting filesystem evms(63,254)
XFS mounting filesystem evms(63,253)


-- 
As any limb well and duly exercised, grows stronger,
the nerves of the body are corroborated thereby. --I. Watts.  .''`.
 We are deB.ORG; You will be freed.                          : :' :
 <URL:http://www.debian.org/social_contract>                 `. `'


<Prev in Thread] Current Thread [Next in Thread>