09-11-2017
i guess I can change my question to ask:
is there a distributed filesystem I can use on a large fiber channel drive that will let multiple servers write to the drive without corrupting data, but that doesn't require a controlling/clustering server like CEPH and GFS2 does?
not sure if I asked that question with the correct terms but maybe it will generate some discussion in the area I'm unsure about, thx!
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have 2 clustered hosts, is it possible for me to issue a netstat command against 1 host from the other ? (4 Replies)
Discussion started by: murphyboy
4 Replies
2. High Performance Computing
Tim Bass
Sat, 17 Nov 2007 04:11:25 +0000
In my earlier*post, A Model For Distributed Event*Processing, I promised to address grid computing, distributed object caching and virtualization, and how these technologies relate to complex event processing.***Some of my readers might forget my earlier... (0 Replies)
Discussion started by: Linux Bot
0 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I wanted to find out that in my database server which filesystems are shared storage and which filesystems are local. Like when I use df -k, it shows "filesystem" and "mounted on" but I want to know which one is shared and which one is local.
Please tell me the commands which I can run... (2 Replies)
Discussion started by: kamranjalal
2 Replies
4. AIX
Hi,
I have done NIM restoration via nim_bosinst a lot of times but I have some doubts on restoring a server which is clustered specifically HACMP. Previously, I don't know the trend but after doing a nim_bosinst, I can see the client's hostname is back to "localhost" rather than its original... (0 Replies)
Discussion started by: depam
0 Replies
5. Solaris
Hi guys!
Could you tell me what's the difference of filesystem of Solaris to filesystem of Windows? I need to compare both.
I have read some over the net but it's so much technical. Could you explain it in a more simpler term? I am new to Solaris. Hope you help me guys.
Thanks! (4 Replies)
Discussion started by: arah
4 Replies
6. AIX
Dear all,
We are facing prolem when we are going to mount AIX filesystem, the system returned the following error
0506-307The AFopen call failed
: A file or directory in the path name does not exist.
But when we ls filesystems in the /etc/ directory it show
-rw-r--r-- 0 root ... (2 Replies)
Discussion started by: m_raheelahmed
2 Replies
7. Solaris
Hello Admins...
How can we migrate a solaris 10 zone which is clustered...??
We have sun cluster 3.2 in our environment. And this is 2 -node cluster
Let me know guys...
Thanks. (0 Replies)
Discussion started by: snchaudhari2
0 Replies
8. Red Hat
Hi all,
I have a 2 node rhel 5.5 cluster (2 server and 1 quorum disk).
I created 2 cluster resources using Luci web console, they are 2 Volume Groups.
I want to remove that cluster and shutdown node 2, but I don't want to loose data on Volume Groups clustered.
How can I remove that... (0 Replies)
Discussion started by: peppeunz
0 Replies
9. UNIX for Beginners Questions & Answers
Hello Experts,
I have a requirement to start and stop weblogic services in a clustered environment.
First i need to start weblogic server and once the server is in Running mode i need to do SSH to other server and there i need to start Node Manager and Managed server, After these two are in... (1 Reply)
Discussion started by: beginner786
1 Replies
CD(9) BSD Kernel Developer's Manual CD(9)
NAME
cd -- CDROM driver for the CAM SCSI subsystem
DESCRIPTION
The cd device driver provides a read only interface for CDROM drives (SCSI type 5) and WORM drives (SCSI type 4) that support CDROM type com-
mands. Some drives do not behave as the driver expects. See the QUIRKS section for information on possible flags.
QUIRKS
Each CD-ROM device can have different interpretations of the SCSI spec. This can lead to drives requiring special handling in the driver.
The following is a list of quirks that the driver recognize.
CD_Q_NO_TOUCH This flag tells the driver not to probe the drive at attach time to see if there is a disk in the drive and find out what
size it is. This flag is currently unimplemented in the CAM cd driver.
CD_Q_BCD_TRACKS This flag is for broken drives that return the track numbers in packed BCD instead of straight decimal. If the drive seems
to skip tracks (tracks 10-15 are skipped) then you have a drive that is in need of this flag.
CD_Q_NO_CHANGER This flag tells the driver that the device in question is not a changer. This is only necessary for a CDROM device with
multiple luns that are not a part of a changer.
CD_Q_CHANGER This flag tells the driver that the given device is a multi-lun changer. In general, the driver will figure this out auto-
matically when it sees a LUN greater than 0. Setting this flag only has the effect of telling the driver to run the initial
read capacity command for LUN 0 of the changer through the changer scheduling code.
CD_Q_10_BYTE_ONLY
This flag tells the driver that the given device only accepts 10 byte MODE SENSE/MODE SELECT commands. In general these
types of quirks should not be added to the cd(4) driver. The reason is that the driver does several things to attempt to
determine whether the drive in question needs 10 byte commands. First, it issues a CAM Path Inquiry command to determine
whether the protocol that the drive speaks typically only allows 10 byte commands. (ATAPI and USB are two prominent exam-
ples of protocols where you generally only want to send 10 byte commands.) Then, if it gets an ILLEGAL REQUEST error back
from a 6 byte MODE SENSE or MODE SELECT command, it attempts to send the 10 byte version of the command instead. The only
reason you would need a quirk is if your drive uses a protocol (e.g., SCSI) that typically does not have a problem with 6
byte commands.
FILES
/sys/cam/scsi/scsi_cd.c is the driver source file.
SEE ALSO
cd(4), scsi(4)
HISTORY
The cd manual page first appeared in FreeBSD 2.2.
AUTHORS
This manual page was written by John-Mark Gurney <jmg@FreeBSD.org>. It was updated for CAM and FreeBSD 3.0 by Kenneth Merry
<ken@FreeBSD.org>.
BSD
March 25, 2014 BSD