Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

freebsd-scsi Digest, Vol 362, Issue 4

0 views
Skip to first unread message

freebsd-sc...@freebsd.org

unread,
Apr 1, 2010, 8:00:30 AM4/1/10
to freebs...@freebsd.org
Send freebsd-scsi mailing list submissions to
freebs...@freebsd.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-scsi
or, via email, send a message with subject or body 'help' to
freebsd-sc...@freebsd.org

You can reach the person managing the list at
freebsd-s...@freebsd.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-scsi digest..."


Today's Topics:

1. Re: How is supposed to be protected the units list?
(Matthew Jacob)
2. Re: adding a "retry command after a delay" error (Matthew Jacob)


----------------------------------------------------------------------

Message: 1
Date: Wed, 31 Mar 2010 19:40:47 -0700
From: Matthew Jacob <m...@feral.com>
Subject: Re: How is supposed to be protected the units list?
To: freebs...@freebsd.org
Message-ID: <4BB407AF...@feral.com>
Content-Type: text/plain; charset=UTF-8; format=flowed

On 3/30/2010 9:14 AM, Matthew Jacob wrote:
> Absolutely. I might also be insane. Working on finding that out.
>> May you please refer precisely to current code snippets (in terms of
>> functions, file, line, etc) in order to better explain this and the
It partly ends up the same as what Alexander found. I like his unit_lock
patch a bit better.

In terms of the xpt_lock.diff patches for da- I don't think this is a
good idea as they stand.

This is part of shutdown code, which can be called as part of panic, so
there is no guarantee about what locks might or might not be held, or
even whether the list being traversed is intact at all.

The problems that I ran into previously in da won't be fixed really by
any of this. The problem here for da(4) is that it is scheduling a task
to run- if the periph is going away, then the task should be cancelled.

Still testing... I'm working on a fault injection case where tons of
arrival/departure events can be thrown at this.

------------------------------

Message: 2
Date: Wed, 31 Mar 2010 20:38:19 -0700
From: Matthew Jacob <m...@feral.com>
Subject: Re: adding a "retry command after a delay" error
To: freebs...@freebsd.org
Message-ID: <4BB4152B...@feral.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

On 3/29/2010 11:42 AM, Matthew Jacob wrote:
> This is something I whipped up for dealing with some
> active/active-after-failover-time systems. I wanted to have a general
> facility to say of an ASC/ASCQ- retry the command, but after a period
> of delay.
>
> Wonder if anyone had comments?
> http://people.freebsd.org/~mjacob/delay_diffs.txt

Any comments?

------------------------------

End of freebsd-scsi Digest, Vol 362, Issue 4
********************************************

0 new messages