mirror of
https://github.com/SCST-project/scst.git
synced 2026-05-14 09:11:27 +00:00
scst: Remove trailing whitespace from documentation and Makefile
git-svn-id: http://svn.code.sf.net/p/scst/svn/trunk@7498 d57e44dd-8a1f-0410-8b47-8ef2f437770f
This commit is contained in:
Bart Van Assche
@@ -107,7 +107,7 @@ For example, this will cause problems in the following situation:
|
||||
7. scst_send_to_midlev returns with SCST_CMD_STATE_RES_NEED_THREAD
|
||||
8. Now, the scst_process_active_cmd will try to reschedule command 0x8000100
|
||||
which is already destroyed at this point !
|
||||
|
||||
|
||||
Can anyone on the list confirm my guess? Or, this situation should never
|
||||
happen because of some other condition which I may have missed? Right
|
||||
now I can't think of any of simple methods to work around the issue,
|
||||
@@ -124,104 +124,104 @@ I have two machines (SCST targets) with the following parameters:
|
||||
- Linux 2.6.21.3, running in 64 bit mode with 16G RAM
|
||||
- SCST trunk version
|
||||
|
||||
On the client side there is a Solaris 10 U3 machine, with the same (chip
|
||||
On the client side there is a Solaris 10 U3 machine, with the same (chip
|
||||
wise) Qlogic controller.
|
||||
|
||||
There is an FC switch between the three machines, and each of the
|
||||
targets are zoned to the client's port in a one-by-one manner, so HBA
|
||||
There is an FC switch between the three machines, and each of the
|
||||
targets are zoned to the client's port in a one-by-one manner, so HBA
|
||||
port 1 sees only target 1 and port 2 sees only target 2.
|
||||
|
||||
The targets are configured with two large sparse files on XFS (8 TB
|
||||
The targets are configured with two large sparse files on XFS (8 TB
|
||||
each, with dd if=/dev/zero of=file bs=1M count=0 seek=8388608).
|
||||
|
||||
In Solaris I do various tests with SVM (Sun's built in volume manager)
|
||||
In Solaris I do various tests with SVM (Sun's built in volume manager)
|
||||
and multiterabyte UFS. Occasionally, there are some strange write
|
||||
errors, where the volume manager drops its volumes and without a VM, a
|
||||
simple UFS fs write can fail too.
|
||||
|
||||
I see various errors logged by the kernel (Solaris'), these are some
|
||||
I see various errors logged by the kernel (Solaris'), these are some
|
||||
examples, both with and without SVM:
|
||||
Jun 21 10:42:14 solaris fctl: [ID 517869 kern.warning] WARNING:
|
||||
Jun 21 10:42:14 solaris fctl: [ID 517869 kern.warning] WARNING:
|
||||
fp(1)::GPN_ID for D_ID=621200 failed
|
||||
Jun 21 10:42:14 solaris fctl: [ID 517869 kern.warning] WARNING:
|
||||
fp(1)::N_x Port with D_ID=621200, PWWN=210000e08b944419 disappeared from
|
||||
Jun 21 10:42:14 solaris fctl: [ID 517869 kern.warning] WARNING:
|
||||
fp(1)::N_x Port with D_ID=621200, PWWN=210000e08b944419 disappeared from
|
||||
fabric
|
||||
Jun 21 10:42:53 solaris scsi: [ID 107833 kern.warning] WARNING:
|
||||
/pci@1,0/pci1022,7450@a/pcie11,105@1,1/fp@0,0/disk@w210000e08b944419,0
|
||||
Jun 21 10:42:53 solaris scsi: [ID 107833 kern.warning] WARNING:
|
||||
/pci@1,0/pci1022,7450@a/pcie11,105@1,1/fp@0,0/disk@w210000e08b944419,0
|
||||
(sd1):
|
||||
Jun 21 10:42:53 solaris SCSI transport failed: reason
|
||||
Jun 21 10:42:53 solaris SCSI transport failed: reason
|
||||
'tran_err': retrying command
|
||||
Jun 21 10:43:06 solaris scsi: [ID 107833 kern.warning] WARNING:
|
||||
/pci@1,0/pci1022,7450@a/pcie11,105@1,1/fp@0,0/disk@w210000e08b944419,0
|
||||
Jun 21 10:43:06 solaris scsi: [ID 107833 kern.warning] WARNING:
|
||||
/pci@1,0/pci1022,7450@a/pcie11,105@1,1/fp@0,0/disk@w210000e08b944419,0
|
||||
(sd1):
|
||||
Jun 21 10:43:06 solaris SCSI transport failed: reason 'timeout':
|
||||
Jun 21 10:43:06 solaris SCSI transport failed: reason 'timeout':
|
||||
retrying command
|
||||
Jun 21 10:43:13 solaris scsi: [ID 107833 kern.notice] Device is gone
|
||||
Jun 21 10:43:13 solaris scsi: [ID 107833 kern.warning] WARNING:
|
||||
/pci@1,0/pci1022,7450@a/pcie11,105@1,1/fp@0,0/disk@w210000e08b944419,0
|
||||
Jun 21 10:43:13 solaris scsi: [ID 107833 kern.warning] WARNING:
|
||||
/pci@1,0/pci1022,7450@a/pcie11,105@1,1/fp@0,0/disk@w210000e08b944419,0
|
||||
(sd1):
|
||||
Jun 21 10:43:13 solaris transport rejected fatal error
|
||||
Jun 21 10:43:13 solaris md_stripe: [ID 641072 kern.warning] WARNING: md:
|
||||
Jun 21 10:43:13 solaris md_stripe: [ID 641072 kern.warning] WARNING: md:
|
||||
d10: write error on /dev/dsk/c2t210000E08B944419d0s6
|
||||
Jun 21 10:43:13 solaris last message repeated 9 times
|
||||
Jun 21 10:43:13 solaris scsi: [ID 243001 kern.info]
|
||||
Jun 21 10:43:13 solaris scsi: [ID 243001 kern.info]
|
||||
/pci@1,0/pci1022,7450@a/pcie11,105@1,1/fp@0,0 (fcp1):
|
||||
Jun 21 10:43:13 solaris offlining lun=0 (trace=0), target=621200
|
||||
Jun 21 10:43:13 solaris offlining lun=0 (trace=0), target=621200
|
||||
(trace=2800004)
|
||||
Jun 21 10:43:13 solaris ufs: [ID 702911 kern.warning] WARNING: Error
|
||||
Jun 21 10:43:13 solaris ufs: [ID 702911 kern.warning] WARNING: Error
|
||||
writing master during ufs log roll
|
||||
Jun 21 10:43:13 solaris ufs: [ID 127457 kern.warning] WARNING: ufs log
|
||||
Jun 21 10:43:13 solaris ufs: [ID 127457 kern.warning] WARNING: ufs log
|
||||
for /mnt changed state to Error
|
||||
Jun 21 10:43:13 solaris ufs: [ID 616219 kern.warning] WARNING: Please
|
||||
Jun 21 10:43:13 solaris ufs: [ID 616219 kern.warning] WARNING: Please
|
||||
umount(1M) /mnt and run fsck(1M)
|
||||
Jun 21 11:08:55 solaris scsi: [ID 107833 kern.warning] WARNING:
|
||||
/pci@1,0/pci1022,7450@a/pcie11,105@1,1/fp@0,0/disk@w210000e08b944419,0
|
||||
Jun 21 11:08:55 solaris scsi: [ID 107833 kern.warning] WARNING:
|
||||
/pci@1,0/pci1022,7450@a/pcie11,105@1,1/fp@0,0/disk@w210000e08b944419,0
|
||||
(sd1):
|
||||
Jun 21 11:08:55 solaris offline or reservation conflict
|
||||
Jun 21 11:09:41 solaris scsi: [ID 107833 kern.warning] WARNING:
|
||||
/pci@1,0/pci1022,7450@a/pcie11,105@1,1/fp@0,0/disk@w210000e08b944419,0
|
||||
Jun 21 11:09:41 solaris scsi: [ID 107833 kern.warning] WARNING:
|
||||
/pci@1,0/pci1022,7450@a/pcie11,105@1,1/fp@0,0/disk@w210000e08b944419,0
|
||||
(sd1):
|
||||
Jun 21 11:09:41 solaris offline or reservation conflict
|
||||
Jun 21 11:09:41 solaris scsi: [ID 107833 kern.warning] WARNING:
|
||||
/pci@1,0/pci1022,7450@a/pcie11,105@1,1/fp@0,0/disk@w210000e08b944419,0
|
||||
Jun 21 11:09:41 solaris scsi: [ID 107833 kern.warning] WARNING:
|
||||
/pci@1,0/pci1022,7450@a/pcie11,105@1,1/fp@0,0/disk@w210000e08b944419,0
|
||||
(sd1):
|
||||
Jun 21 11:09:41 solaris offline or reservation conflict
|
||||
Jun 21 11:09:41 solaris scsi: [ID 107833 kern.warning] WARNING:
|
||||
/pci@1,0/pci1022,7450@a/pcie11,105@1,1/fp@0,0/disk@w210000e08b944419,0
|
||||
Jun 21 11:09:41 solaris scsi: [ID 107833 kern.warning] WARNING:
|
||||
/pci@1,0/pci1022,7450@a/pcie11,105@1,1/fp@0,0/disk@w210000e08b944419,0
|
||||
(sd1):
|
||||
Jun 21 11:09:41 solaris i/o to invalid geometry
|
||||
Jun 21 11:09:41 solaris scsi: [ID 107833 kern.warning] WARNING:
|
||||
/pci@1,0/pci1022,7450@a/pcie11,105@1,1/fp@0,0/disk@w210000e08b944419,0
|
||||
Jun 21 11:09:41 solaris scsi: [ID 107833 kern.warning] WARNING:
|
||||
/pci@1,0/pci1022,7450@a/pcie11,105@1,1/fp@0,0/disk@w210000e08b944419,0
|
||||
(sd1):
|
||||
Jun 21 11:09:41 solaris offline or reservation conflict
|
||||
Jun 21 11:09:41 solaris scsi: [ID 107833 kern.warning] WARNING:
|
||||
/pci@1,0/pci1022,7450@a/pcie11,105@1,1/fp@0,0/disk@w210000e08b944419,0
|
||||
Jun 21 11:09:41 solaris scsi: [ID 107833 kern.warning] WARNING:
|
||||
/pci@1,0/pci1022,7450@a/pcie11,105@1,1/fp@0,0/disk@w210000e08b944419,0
|
||||
(sd1):
|
||||
Jun 21 11:09:41 solaris i/o to invalid geometry
|
||||
Jun 21 11:09:41 solaris scsi: [ID 107833 kern.warning] WARNING:
|
||||
/pci@1,0/pci1022,7450@a/pcie11,105@1,1/fp@0,0/disk@w210000e08b944419,0
|
||||
Jun 21 11:09:41 solaris scsi: [ID 107833 kern.warning] WARNING:
|
||||
/pci@1,0/pci1022,7450@a/pcie11,105@1,1/fp@0,0/disk@w210000e08b944419,0
|
||||
(sd1):
|
||||
Jun 21 11:09:41 solaris offline or reservation conflict
|
||||
Jun 21 11:09:41 solaris scsi: [ID 107833 kern.warning] WARNING:
|
||||
/pci@1,0/pci1022,7450@a/pcie11,105@1,1/fp@0,0/disk@w210000e08b944419,0
|
||||
Jun 21 11:09:41 solaris scsi: [ID 107833 kern.warning] WARNING:
|
||||
/pci@1,0/pci1022,7450@a/pcie11,105@1,1/fp@0,0/disk@w210000e08b944419,0
|
||||
(sd1):
|
||||
Jun 21 11:09:41 solaris i/o to invalid geometry
|
||||
Jun 21 11:09:43 solaris scsi: [ID 107833 kern.warning] WARNING:
|
||||
/pci@1,0/pci1022,7450@a/pcie11,105@1,1/fp@0,0/disk@w210000e08b944419,0
|
||||
Jun 21 11:09:43 solaris scsi: [ID 107833 kern.warning] WARNING:
|
||||
/pci@1,0/pci1022,7450@a/pcie11,105@1,1/fp@0,0/disk@w210000e08b944419,0
|
||||
(sd1):
|
||||
Jun 21 11:09:43 solaris offline or reservation conflict
|
||||
Jun 21 11:09:43 solaris scsi: [ID 107833 kern.warning] WARNING:
|
||||
/pci@1,0/pci1022,7450@a/pcie11,105@1,1/fp@0,0/disk@w210000e08b944419,0
|
||||
Jun 21 11:09:43 solaris scsi: [ID 107833 kern.warning] WARNING:
|
||||
/pci@1,0/pci1022,7450@a/pcie11,105@1,1/fp@0,0/disk@w210000e08b944419,0
|
||||
(sd1):
|
||||
Jun 21 11:09:43 solaris SYNCHRONIZE CACHE command failed (5)
|
||||
|
||||
I don't see anything in the dmesg on the target side.
|
||||
|
||||
After these errors SCST seems to be dead. I can't unload its modules and
|
||||
After these errors SCST seems to be dead. I can't unload its modules and
|
||||
can't communicate it via /proc.
|
||||
A simple cat vdisk just waits and waits.
|
||||
|
||||
Could you please help? What should I set/collect/send in this case to
|
||||
Could you please help? What should I set/collect/send in this case to
|
||||
help resolving this issue?
|
||||
|
||||
======================================================================
|
||||
|
||||
@@ -60,7 +60,7 @@ Summary of changes between versions 1.0.1 and 1.0.2
|
||||
/sys/module/scst and /sys/module/scst_vdisk correspondingly
|
||||
|
||||
- Shared between devices SGV caches were implemented
|
||||
|
||||
|
||||
- Possibilities to operate with single size entries as well as control of
|
||||
the reclamation time added to the SGV cache
|
||||
|
||||
@@ -69,7 +69,7 @@ Summary of changes between versions 1.0.1 and 1.0.2
|
||||
- INIT ELEMENT STATUS WRANGE added to the list of known commands.
|
||||
|
||||
- Races on scst_user devices cleanup fixed
|
||||
|
||||
|
||||
- Implemented abort on timeout of stuck in tgt hardware commands
|
||||
|
||||
- Automatic sessions reassignment implemented with corresponding atomic
|
||||
@@ -82,7 +82,7 @@ Summary of changes between versions 1.0.1 and 1.0.2
|
||||
|
||||
- Update for 2.6.30
|
||||
|
||||
- Other bug fixes and cleanups
|
||||
- Other bug fixes and cleanups
|
||||
|
||||
|
||||
Summary of changes between versions 1.0.0 and 1.0.1
|
||||
@@ -95,12 +95,12 @@ Summary of changes between versions 1.0.0 and 1.0.1
|
||||
- Support for variable length CDB added
|
||||
|
||||
- Support for Async. Event Notifications added
|
||||
|
||||
|
||||
- Implemented "plug-and-play" notifications about new devices in security
|
||||
groups, deleted devices from security groups and changed size of a
|
||||
device. They can be delivered either through AENs (if supported), or
|
||||
Unit Attentions.
|
||||
|
||||
|
||||
- New command "resync_size" added to scst_vdisk proc interface to tell
|
||||
scst_vdisk to reread size of the corresponding device after it was
|
||||
changed
|
||||
@@ -117,13 +117,13 @@ Summary of changes between versions 1.0.0 and 1.0.1
|
||||
- scst_unregister_session_ex() removed, since there are no users of it
|
||||
|
||||
- New functions added to scst_user interface:
|
||||
|
||||
|
||||
* SCST_USER_UNREGISTER_DEVICE - to unregister device, flush mem reuse
|
||||
(SGV) cache and send UCMD_STATE_ON_CACHE_FREEING notifications for all
|
||||
freed buffers to the user space handler. Simple device close doesn't
|
||||
allow that, so all the cached buffers might look as "leaked" from the
|
||||
user space handler POV.
|
||||
|
||||
|
||||
* SCST_USER_FLUSH_CACHE - to flush mem reuse (SGV) cache and send
|
||||
UCMD_STATE_ON_CACHE_FREEING notifications for all freed buffers to
|
||||
the user space handler
|
||||
@@ -298,7 +298,7 @@ Summary of changes between versions 0.9.4 and 0.9.5
|
||||
|
||||
- More intelligent IO flow control implemented.
|
||||
|
||||
- Fixed broken CDROM FILEIO. Before that it always reported
|
||||
- Fixed broken CDROM FILEIO. Before that it always reported
|
||||
"No medium found"
|
||||
|
||||
- Data synchronization fixes and improvements in FILEIO. Added FUA
|
||||
@@ -411,7 +411,7 @@ Summary of changes between versions 0.9.2 and 0.9.3-pre1
|
||||
* New CDROM FILEIO handler added.
|
||||
|
||||
* Now per-session threads created to improve concurrent performance.
|
||||
|
||||
|
||||
* New flags added that allow using virtual devices as read only,
|
||||
with write through caching or in O_DIRECT mode.
|
||||
|
||||
@@ -422,30 +422,30 @@ Summary of changes between versions 0.9.2 and 0.9.3-pre1
|
||||
- SCSI processor (type 3) dev handler added.
|
||||
|
||||
- Sessions unregistration contexts cleanup.
|
||||
|
||||
- Dev handler's on_free_cmd() was dropped. Target driver's flag
|
||||
|
||||
- Dev handler's on_free_cmd() was dropped. Target driver's flag
|
||||
"thread_per_session" was dropped as well.
|
||||
|
||||
|
||||
- Internal locking partially redone.
|
||||
|
||||
|
||||
- A lot of stability/bug fixes, cleanups and performance improvements.
|
||||
|
||||
Summary of changes between versions 0.9.1 and 0.9.2
|
||||
---------------------------------------------------
|
||||
|
||||
- 2.6 support, developed and tested on 2.6.7.
|
||||
|
||||
|
||||
- FILEIO/BLKDEV virtual disk device handler added. See main README for
|
||||
details.
|
||||
|
||||
|
||||
- /proc updates, "trace_log_level" entry added to change traced
|
||||
events on the fly.
|
||||
|
||||
|
||||
- Some internal interfaces changed, see the documentation.
|
||||
|
||||
|
||||
- Device handlers' source code layout changed, all device handlers
|
||||
live in one subdirectory now.
|
||||
|
||||
|
||||
- Crash on memory allocation failure while building SG data vector
|
||||
fixed.
|
||||
|
||||
@@ -457,11 +457,11 @@ Summary of changes between versions 0.9.0a and 0.9.1
|
||||
- scst_debug.* files are also installed together with scsi_tgt.h
|
||||
(required by QLA2x00 target and could be useful for other target
|
||||
drivers)
|
||||
|
||||
|
||||
- CDB length for unknown commands (e.g. vendor ones) is now determined
|
||||
from CDB
|
||||
|
||||
|
||||
- Race with the commands serialization on one drive fixed
|
||||
|
||||
|
||||
- Cleanup
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
#
|
||||
# Common makefile for SCSI target mid-level and its drivers
|
||||
#
|
||||
#
|
||||
# Copyright (C) 2015 - 2018 Vladislav Bolkhovitin <vst@vlnb.net>
|
||||
# Copyright (C) 2004 - 2005 Leonid Stoljar
|
||||
# Copyright (C) 2007 - 2018 Western Digital Corporation
|
||||
|
||||
@@ -45,4 +45,4 @@ References
|
||||
* Stefan Berger, [SCST and DRBD in Dual Primary Mode], DRBD users mailing
|
||||
list, June 2010.
|
||||
* Bart Van Assche [SCST and DRBD in Dual Primary Mode], SCST Developers
|
||||
Mailing List, May 2011.
|
||||
Mailing List, May 2011.
|
||||
|
||||
Reference in New Issue
Block a user