Re: `bioctl sd0` reports bioctl: BIOCINQ: Invalid argument

Marco Peereboom wrote: Yeah rebooting will probably fix this. It looks as if the last bio command never completed and now it is blocking access. Now why this happened I can't tell you based on this amount of information. Would you be interested in any further information before (or after) I

Re: `bioctl sd0` reports bioctl: BIOCINQ: Invalid argument

Actually, no. Lots has changed since 3.8. If you can reproduce this on 4.0 it becomes interesting again. On Mon, Nov 27, 2006 at 08:08:20PM +0100, [EMAIL PROTECTED] wrote: Marco Peereboom wrote: Yeah rebooting will probably fix this. It looks as if the last bio command never completed and

Re: `bioctl sd0` reports bioctl: BIOCINQ: Invalid argument

Ok, I understand that. Thanks a lot for your help! /Alexander Marco Peereboom wrote: Actually, no. Lots has changed since 3.8. If you can reproduce this on 4.0 it becomes interesting again. On Mon, Nov 27, 2006 at 08:08:20PM +0100, [EMAIL PROTECTED] wrote: Marco Peereboom wrote: Yeah

`bioctl sd0` reports bioctl: BIOCINQ: Invalid argument

Hi all. Minor panic here. Before reading further, please note that this machine is still running 3.8 (and, yes, will be updated as soon as possible). As part of my daily.local, I have a RAID status check using `bioctl sd0`. Some days ago, it started reporting RAID status: bioctl: BIOCINQ:

Re: `bioctl sd0` reports bioctl: BIOCINQ: Invalid argument

Yeah rebooting will probably fix this. It looks as if the last bio command never completed and now it is blocking access. Now why this happened I can't tell you based on this amount of information. On Sun, Nov 26, 2006 at 12:57:32PM +0100, Alexander Hall wrote: Hi all. Minor panic here.