On 08/17/2017 03:25 PM, Tejun Heo wrote:
> Hello,
>
> On Thu, Aug 17, 2017 at 03:18:06PM +0200, Bernd Schubert wrote:
>> So for Gionatan the root cause was an instable power supply, but in my
>> case there wasn't any power loss, there were just failed sata commands.
&
Hello Tejun,
On 08/17/2017 02:48 PM, Tejun Heo wrote:
> Hello,
>
> On Thu, Aug 17, 2017 at 11:24:22AM +0200, Bernd Schubert wrote:
>>> More concerning is the fact that these undetected errors can make their
>>> way even when the higher application consistently calls
[This seems to be libata error handling and not scsi, so I added more CCs]
On 08/17/2017 12:27 AM, Gionatan Danti wrote:
> Hi list,
> some time ago, I had a filesystem corruption on a simple, two disks
> RAID1 MD array. On the affected machine, /var/log/messages shown some
> "failed command: WRITE
On 09/27/2015 12:28 PM, Gionatan Danti wrote:
> Il 23-09-2015 17:18 Emmanuel Florac ha scritto:
>>
>> Use XFS. XFS won't let you mount it several time on different machines
>> without various "force" options.
>> Alternatively, use a cluster-aware FS like ocfs2. Ocfs2 is quite easy
>> to set up.
>
> The second patch tweaks the SCSI disk driver to prefer WRITE SAME w/
> UNMAP instead of the UNMAP command since the former has deterministic
> behavior.
I have seen data corruption on an Intel SSD 510 after sending WRITE SAME
UNMAP. As far as I remember, these disks ignore writes after sending
t
On 02/12/2014 03:27 AM, Kurt Miller wrote:
I can report that the Samsung 840 Pro*does* support trim on the LSI
SAS2008. As suspected it supports deterministic read zeros after trim.
One other thing to note, in my testing the P16 LSI firmware has broken
trim support. P14 and P15 report incorrect
u8 scsi_io_cb_idx;
diff --git a/drivers/scsi/mpt2sas/mpt2sas_scsih.c
b/drivers/scsi/mpt2sas/mpt2sas_scsih.c
index 7f0af4f..d502728 100644
--- a/drivers/scsi/mpt2sas/mpt2sas_scsih.c
+++ b/drivers/scsi/mpt2sas/mpt2sas_scsih.c
@@ -127,6 +127,11 @@ static int disable_discovery =
Hello Joseph,
On 10/29/2013 08:21 PM, Joseph Salisbury wrote:
Hi Martin,
A bug was opened against the Ubuntu kernel[0]. After a kernel bisect,
it was found that reverting the following commit resolved this bug:
commit 66c28f97120e8a621afd5aa7a31c4b85c547d33d
Author: Martin K. Petersen
Date:
On 09/26/2013 04:42 PM, Martin K. Petersen wrote:
"Bernd" == Bernd Schubert writes:
Bernd,
Bernd> Both types of systems we have in-house neither block limits vpd
Bernd> nor READ_CAP16 return anything that would indicate discard is
Bernd> supported. But UNMAP and WRITE SAME
On 09/26/2013 07:39 AM, Douglas Gilbert wrote:
On 13-09-25 08:44 PM, Martin K. Petersen wrote:
"Bernd" == Bernd Schubert writes:
Hey Bernd,
Bernd> I'm afraid we have another problem. I'm currently working on to
Bernd> get discard working for our LSI2008 HBAs wit
On 09/24/2013 03:49 PM, Martin K. Petersen wrote:
>> "Mike" == Mike Snitzer writes:
>
> Mike> So are there drives like this?:
> Mike> 1) don't support RSOC
> Mike> 2) do support WRITE SAME
> Mike> 3) do populate VPD page with either WRITE SAME w/ discard bit set
> Mike>or UNMAP?
>
> Yes.
On 09/24/2013 02:35 PM, KY Srinivasan wrote:
-Original Message-
From: Jack Wang [mailto:xjtu...@gmail.com]
Sent: Tuesday, September 24, 2013 5:08 AM
To: KY Srinivasan
Cc: Greg KH; linux-ker...@vger.kernel.org; de...@linuxdriverproject.org;
oher...@suse.com; jbottom...@parallels.com; h.
From: Bernd Schubert
Somehow older areca firmware versions have issues with
scsi_get_vpd_page() and a large buffer, the firmware
seems to crash and the scsi error-handler will start endless
recovery retries.
Limiting the buf-size to 64-bytes fixes this issue with older
firmware versions (<1
James Bottomley wrote:
>[cc to linux-scsi added]
>On Sun, 2013-09-22 at 16:27 +0200, Christian Bahls - gmail.com wrote:
>> Dear all,
>>
>> Looks like i have been bitten by the above mentioned commit.
>
>Just from a practical point of view, I only really work upstream, so
>this commit id doesn't s
On 08/31/2013 09:48 PM, Nix wrote:
> On 31 Aug 2013, Greg KH said:
>> On Fri, Aug 30, 2013 at 11:01:56AM +0100, Nix wrote:
>>> On 1 Aug 2013, Bernd Schubert said:
>>>
>>>> Once I noticed that scsi_get_vpd_page() works fine from other function
>>>
Martin,
sorry for my late reply, I entirely lost track of this (customer issues,
vacation, lots of main work, ...).
On 08/02/2013 05:00 AM, Martin K. Petersen wrote:
>>>>>> "Bernd" == Bernd Schubert writes:
>
> Bernd,
>
> Bernd> Once I noticed tha
On 08/01/2013 06:04 PM, Nix wrote:
On 1 Aug 2013, Bernd Schubert verbalised:
On 07/30/2013 11:20 PM, Nix wrote:
On 30 Jul 2013, Bernd Schubert told this:
On 07/30/2013 02:56 AM, Nix wrote:
On 30 Jul 2013, Douglas Gilbert outgrape:
Please supply the information that Martin Petersen asked
On 07/30/2013 11:20 PM, Nix wrote:
On 30 Jul 2013, Bernd Schubert told this:
On 07/30/2013 02:56 AM, Nix wrote:
On 30 Jul 2013, Douglas Gilbert outgrape:
Please supply the information that Martin Petersen asked
for.
Did it in private IRC (the advantage of working for the same division of
Whoops, the title is wrong, it should have been:
[PATCH] scsi disk: Limit get_vpd_page buf size
On 08/01/2013 04:34 PM, Bernd Schubert wrote:
Once I noticed that scsi_get_vpd_page() works fine from other function
calls and that it is not 0x89, but already 0x0 that fails fixing it became
easy
Once I noticed that scsi_get_vpd_page() works fine from other function
calls and that it is not 0x89, but already 0x0 that fails fixing it became
easy.
Nix, any chance you could verify it also works for you?
From: Bernd Schubert
Somehow older areca firmware versions have issues with
On 07/31/2013 05:15 AM, Martin K. Petersen wrote:
>>>>>> "Bernd" == Bernd Schubert writes:
>
> Bernd,
>
>>> Product revision level: R001
>
> It's clearly not verbatim passthrough...
>
> Bernd> Besides the firmware, the differ
On 07/30/2013 02:56 AM, Nix wrote:
On 30 Jul 2013, Douglas Gilbert outgrape:
Please supply the information that Martin Petersen asked
for.
Did it in private IRC (the advantage of working for the same division of
the same company!)
I didn't realise the original fix was actually implemented to
On 07/30/2013 01:34 AM, Martin K. Petersen wrote:
"Nix" == Nix writes:
Bernd,
Nix> I can now confirm that reverting this commit causes this problem to
Nix> go away, and my machine boots fine again.
Can you please send me the output of sq_inq with your 1.49 firmware?
I made a tweak that all
On 07/29/2013 03:05 PM, Nix wrote:
On 29 Jul 2013, Bernd Schubert said:
Hi Nick,
On 07/29/2013 12:10 PM, Nick Alcock wrote:
arcmsr0: abort device command of scsi id = 0 lun = 1
arcmsr0: abort device command of scsi id = 0 lun = 0
arcmsr: executing bus reset eh.num_resets=0, num_
Hi Nick,
On 07/29/2013 12:10 PM, Nick Alcock wrote:
My server's ARC-1210 has been working fine for years, but when I
upgraded from 3.10.1, it started failing:
Instead of
[0.784044] Areca RAID Controller0: F/W V1.46 2009-01-06 & Model ARC-1210
[0.804028] scsi0 : Areca SATA Host Adapter
On 06/07/2013 04:15 AM, Martin K. Petersen wrote:
"Bernd" == Bernd Schubert writes:
max_t(unsigned long, max, SD_MAX_WS10_BLOCKS);
Bernd> Max? Not min_t()?
Brain fart. Updated patch with a few other adjustments.
I have tested this on a couple of JBODs with a mishmash of
On 06/05/2013 09:14 PM, Martin K. Petersen wrote:>>>>>> "Bernd" == Bernd
Schubert writes:
>
> Bernd> The md layer currently cannot handle failed WRITE_SAME commands
> Bernd> and the initial easiest fix is to check if the device supports
> B
#x27; (ctx:WxW)
> #48: FILE: drivers/scsi/sd.h:87:
> + unsignedws10 : 1;
> ^
If someone wants me, I can send another patch to fix the other
lines first.
scsi: Check if the device support WRITE_SAME_10
From: Bernd Schubert
The md layer curre
On 06/05/2013 12:02 PM, Bernd Schubert wrote:
On 06/04/2013 05:39 PM, Joe Lawrence wrote:
Just curious, what type drives were in your RAID and what does
/sys/class/scsi_disk/*/max_write_same_blocks report? If you have a spare
drive to test, maybe you could try a quick sg_write_same command to
Even Nagios complains
> about the machine being down while rsync is running.
do you have the write-back cache of the controller enabled for your disks?
When you disable this cache, the controller will also disable the disks,
cause a write-performance between 3 to 8MB/s per disks.
Cheer
On Wednesday 16 January 2008 19:27:43 James Bottomley wrote:
> On Wed, 2008-01-16 at 19:13 +0100, Bernd Schubert wrote:
> > Hi,
> >
> > I already grepped, but I don't find the definition of
> >
> > return code = 0x0007
> >
> >
> > Just g
error handling patches in queue for 2.6.22, I would like to
know if I would have catched this error, but 0x0007 is pretty meaningless
for me :(
Thanks,
Bernd
--
Bernd Schubert
Q-Leap Networks GmbH
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the bo
On Wednesday 02 January 2008 20:07:51 Moore, Eric wrote:
> On Wednesday, January 02, 2008 11:54 AM, Bernd Schubert wrote:
> > I complained about this before, but always got ignored.
> > Please not this time.
>
> Sorry, I didn't see your email before today.
>
> &
logging_level", but this doesn't
reveal anything.
Please, we really need to fix this, as this is really troublesome in
production situation. Some hints for further debugging should be suffienct
for now.
Thanks,
Bernd
--
Bernd Schubert
Q-Leap Networks GmbH
-
To unsubscribe from t
s is really troublesome in
production situation. Some hints for further debugging should be suffienct
for now.
Thanks,
Bernd
--
Bernd Schubert
Q-Leap Networks GmbH
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTEC
e_t last_recovery; /* last time eh completed */
+ int n_errors; /* number failures within
+time limit */
wait_queue_head_t host_wait;
struct scsi_host_template *hostt;
struct
2349.908019] [] system_call+0x7e/0x83
[ 2349.913326] [<2b351a9c92aa>]
[ 2349.916713]
Thanks,
Bernd
--
Bernd Schubert
Q-Leap Networks GmbH
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info
in domain validation because of
> > > a resource starvation issue, but I know of none where everything hangs
> > > just after error recovery completes.
> >
> > Since still not much happend to solve this bug, shall I create a bugzilla
> > entry?
>
> Sure .
On Friday 14 December 2007 13:22:55 Matthew Wilcox wrote:
> On Fri, Dec 14, 2007 at 01:04:12PM +0100, Bernd Schubert wrote:
> > PS: Do you have some links to scsi and SPI specs?
>
> The final versions are available for a fee from ANSI. However,
> you can download the final draft
Hello James,
On Thursday 13 December 2007 15:18:33 James Bottomley wrote:
> On Wed, 2007-12-12 at 18:54 +0100, Bernd Schubert wrote:
> > [Hmm, resending since mail after more than 30min still not on the ML,
> > maybe the attachment was too large? I have uploaded the log to
> &g
On Thursday 13 December 2007 15:18:33 James Bottomley wrote:
> On Wed, 2007-12-12 at 18:54 +0100, Bernd Schubert wrote:
> > [Hmm, resending since mail after more than 30min still not on the ML,
> > maybe the attachment was too large? I have uploaded the log to
> > http://www.
15:36 +0100, Bernd Schubert wrote:
> > On Wednesday 12 December 2007 14:39:27 Matthew Wilcox wrote:
> > > On Wed, Dec 12, 2007 at 01:54:14PM +0100, Bernd Schubert wrote:
> > > > below is a patch introducing device recovery, trying to prevent i/o
> > > > error
On Wednesday 12 December 2007 14:39:27 Matthew Wilcox wrote:
> On Wed, Dec 12, 2007 at 01:54:14PM +0100, Bernd Schubert wrote:
> > below is a patch introducing device recovery, trying to prevent i/o
> > errors when a DID_NO_CONNECT or SOFT_ERROR does happen.
>
> Why doesn
5:0:2: Ending Domain Validation
Hmm, somehow related to sdev->inquiry_len, but isn't it the task of
spi_schedule_dv_device() and subfunctions to do that properly?
Any comments, hints and help is appreciated.
Signed-of-by: Bernd Schubert <[EMAIL PROTECTED]>
Index: linux-2.6.2
.
scsi_dispatch_cmd() doesn't seem to be suffient.
I would be greatful for any hints.
Signed-off-by: Bernd Schubert <[EMAIL PROTECTED]>
Index: linux-2.6.22/drivers/scsi/scsi_error.c
===
--- linux-2.6.22.orig/drivers/scs
Hello Andrew,
thanks for your help!
On Friday 07 December 2007 02:09:11 Andrew Morton wrote:
> On Wed, 5 Dec 2007 21:44:54 +0100
>
> Bernd Schubert <[EMAIL PROTECTED]> wrote:
> > after scsi-recovery a system here went into some kind lock-up, everything
> > seems t
some
time.
Any hints and suggestions are highly appreciated.
Thanks in advance,
Bernd
--
Bernd Schubert
Q-Leap Networks GmbH
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi,
we have to deal here with troublesome Infortrend devices. These units do
have 2 independent scsi channels, which are unfortunately not so
independent as they should be.
Now we have two different systems (lets say OSS-1 and OSS-2) connected to
each of the scsi-channels and both channels are ser
. If there are some tests/reboots/whatever
I could do, it would be best to do it shortly after the scheduled reboot.
Actually I now would have attempted to port your mod15 patch
(http://home-tj.org/wiki/index.php/Sil_m15w#Patches) to 2.6.23, hoping it
would solve Soerens problem and ours as we
On Friday 12 October 2007 23:08:21 Jeff Garzik wrote:
> Bernd Schubert wrote:
> > a) 2.6.23 + sil-patch I posted, this is on a customer system (though my
> > former group), I wouldn't like to use -mm there.
> >
> > b) .config is attached
> >
> > c) attac
On Thursday 11 October 2007 17:04:45 Jeff Garzik wrote:
> Bernd Schubert wrote:
> > On Thursday 11 October 2007 16:19:37 Jeff Garzik wrote:
> >> 1) Just about the only valid optimization is to ensure that only the
> >> write path must be limited to small chunks, not both
a
corruption as without the patch. I know this is only an obersavation and no
definite prove...
Also, this is with 3114, maybe this chip behaves a bit different than 3112?
Thanks,
Bernd
--
Bernd Schubert
Q-Leap Networks GmbH
-
To unsubscribe from this list: send the line "unsubscribe linux-scs
| 58 ++--
include/linux/libata.h|6 +++
3 files changed, 62 insertions(+), 11 deletions(-)
Signed-off-by: Bernd Schubert <[EMAIL PROTECTED]>
Index: linux-2.6.23-rc9/drivers/ata/libata-
/s to 20-25MB/s. But better safe than
lost data or damaged filesystem.
Signed-off-by: Bernd Schubert <[EMAIL PROTECTED]>
Index: linux-2.6.23-rc9/drivers/ata/sata_sil.c
===
--- linux-2.6.23-rc9.orig/drivers/ata/sata_sil.c
This will add the Seagate ST3250820AS to the mod15 blacklist.
I think this is rather trivial and should go into any any release as soon as
possible, since there will be data corruption without it for this disk.
Signed-off-by: Bernd Schubert <[EMAIL PROTECTED]>
Index: linux-2.6.23-rc9/d
On Wednesday 10 October 2007 11:12:20 Bernd Schubert wrote:
> On Monday 08 October 2007 17:09:17 Bernd Schubert wrote:
> > [sorry for sending twice, but after I read the sil sources, I see the
> > mail address had been wrong]
> >
> > Hi,
> >
> > somehow the s
On Monday 08 October 2007 17:09:17 Bernd Schubert wrote:
> [sorry for sending twice, but after I read the sil sources, I see the mail
> address had been wrong]
>
> Hi,
>
> somehow the sil3114 causes data corruption with some (newer?) disks. Simply
> filling the filesystem w
: p1 p2 p3
[ 345.187133] sd 1:0:0:0: Attached scsi disk sdb
The ST3250820AS data on the ST3250820AS disk will suffer from data corruption,
but the data on the older ST3200822AS will *not*.
kernel versions tested: 2.6.15-2.6.20
Any ideas how to proceed?
Thanks,
Bernd
--
Bernd Schubert
Q-Leap
disk will suffer from data corruption,
but the data on the older ST3200822AS will *not*.
kernel versions tested: 2.6.15-2.6.20
Any ideas how to proceed?
Thanks,
Bernd
--
Bernd Schubert
Q-Leap Networks GmbH
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the
13:
../linux_compat.h:9:30: error: scsi/scsi_device.h: No such file or directory
../linux_compat.h:10:28: error: scsi/scsi_cmnd.h: No such file or directory
The kernel_headers in Debian don't have these files and including the header
files directly from the kernel tree doesn't work.
Do y
4-bit, non-prefetchable) [size=64K]
Expansion ROM at fc80 [disabled] [size=1M]
Capabilities: [50] Power Management version 2
Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/0
Enable-
Capabilities: [68]
--
Bernd Schubert
PCI / Theoretische Chemie
Unive
Hi,
recently I asked about problems to expect with >2TB devices and the answer
of Douglas made me hope we won't get any problems this time.
Unfortunately, we get I/O errors on accessing the device.
The unit is called transtec PV610S, which is actually an Infortrend EonStor
A16U-G2421-1 device.
P
r
> responding again.
For a non-scsi protocol expert those scsi card dumps really don't say
anything :(
Thanks again,
Bernd
--
Bernd Schubert
Physikalisch Chemisches Institut / Theoretische Chemie
Universität Heidelberg
INF 229
69120 Heidelberg
-
To unsubscribe from this list: send the line
Hi,
we have not bought the device yet, but presently in the process to do so.
Before we buy it, I want to know about problems in advance...
I'm somewhat worried about this problem report
http://lists.freebsd.org/pipermail/aic7xxx/2006-January/thread.html#4280
Especially as I don't see a final sol
in if we better should reboot again and/or try to
use a newer kernel or can leave the system as it is without another reboot.
Of course, we would also like to know the reason for the oops. Any help is
appreciated.
Thanks in advance,
Bernd
--
Bernd Schubert
Physikalisch Chemisches I
65 matches
Mail list logo
