| To: | Dave Chinner <david@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: handling device or resource busy errors. |
| From: | Ed Peschko <horos22@xxxxxxxxx> |
| Date: | Wed, 9 Dec 2015 23:58:41 -0800 |
| Cc: | xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=PnYkXDUZFfeBUT1fcJ1ogwta1Yg+r/Nh+ZZpNxVXb2k=; b=kd5q8b4tIqf5UKmTYAXpwgTjQvQK0F/tVibyiPfMi3tgDIWJgYifNVyaFCwb0ZSivc mxVeu4a0DYIXhIEKfOocUDg76S/9raDIOAM9co1r++zRiEDGJP4fkj1FnsRiR9Jit7qF xJYu4O9e1YjjA/yM61qZSOoj0VYkn4FORFeMaMTc0geZNydW+fKbKlLOUeib2lhrAzFQ tr8LT5IBkEznHtZB/y7/qlQN026+ipaRspSsWnxymnAK35lX4w0JS1WBrxLEFvGw7wr3 VcnRBXzO+l72z5UhURvnHD/2h3X2jeNs78wuU1VfyqXjb2IL7utj34KdZLU63PAZP4Zr 5a+A== |
| In-reply-to: | <20151210021343.GI19802@dastard> |
| References: | <CACQ+YcuwWv8g5zHk2sMfN_uRPGnW8Xb8WT6NGOLGigN2+0Toag@xxxxxxxxxxxxxx> <20151210021343.GI19802@dastard> |
|
Dave,
futex comes from doing a simple strace, which showed the futex as the call that was being blocked. My fear is that it is a holdover from an old, dead process; we went through eachÂprocess on the system and lsof -p'd it, didn't see anything. Thanks for the suggestion of sysrq btw, I'll try that the next time I have access to the box, but waiting doesn't help.Also, ÂI don't see in sysrq the actual ability to *kill* wayward locks however; but it will a great help us track down the underlying issue. Thanks, Ed The one thing I don't see in sysrq is a way to As for sys |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: handling device or resource busy errors., Dave Chinner |
|---|---|
| Next by Date: | I am Dr. Haruna Bello,, drharunabello868@xxxxxxxxx |
| Previous by Thread: | Re: handling device or resource busy errors., Dave Chinner |
| Next by Thread: | Re: handling device or resource busy errors., Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |