Sponsored Content
Operating Systems Linux Ubuntu Samba share on software raid1 Post 303022381 by hicksd8 on Friday 31st of August 2018 03:27:41 AM
Old 08-31-2018
There is no need to be confused because a RAID is present.

When you create a RAID1 (mirror) the pair of disks are afterwards managed as a single drive. The second disk becomes invisible.

Having a RAID1 has no bearing or influence on what the storage is used for, Samba or anything else.

The RAID1 is managed using a single device (/dev/dsk/<whatever>) for mounting/dismounting and will mount/dismount like any other single drive.

So once the RAID1 is formed, ignore the fact it's a RAID and treat it like any other single disk.

You can mount the space anywhere you like and use the storage like any other storage.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How can i set up Software disk mirroring(Raid1) in SCO 5.0.5 with two SCSI harddisk ?

thank u very much, (1 Reply)
Discussion started by: coralsea
1 Replies

2. Linux

Facing problem in Samba share

Hi, I am facing problem while accessing samba share on Linux 5.1 from windows, though I have done the same configuration on Linux 4 (Update 2), on Red Hat 4.0 it is working but while on Linux 5.1 these configuration are not working, I have disabled the firewall also. Kindly suggest me... (1 Reply)
Discussion started by: manoj.solaris
1 Replies

3. Linux

Samba share script

Hi everyone! I'm trying to run a script when a folder is shared and when it stop being shared. Is there something like .start_share or .stop_share scripts in Samba where I could run some commands?:confused: edit: maybe with a wrapper in smbmount but I share folders via nautilus. Any ideas? (0 Replies)
Discussion started by: funyotros
0 Replies

4. UNIX for Advanced & Expert Users

Problems between a HP UX 11.31 Samba share and Windows 7...

Hi I have an issue with a client. He was able to use his mounted Samba share for a long time. However, a couple of days ago, he wasn't able to access all of his files all of a sudden. He still see's the share and majority of the files, but not some that he needs. I checked with Secure CRT on... (1 Reply)
Discussion started by: zixzix01
1 Replies

5. Solaris

samba issue: one samba share without password prompting and the others with.

Hi All, I've been trying to configure samba on Solaris 10 to allow me to have one share that is open and writable to all users and have the rest of my shares password protected by a generic account. If I set my security to user, my secured shares work just fine and prompt accordingly, but when... (0 Replies)
Discussion started by: ideal2545
0 Replies

6. Red Hat

How to Map AD groups to Samba share?

I am setup a samba share server which is authenticating from Active Directory. I am able to access the share with AD user but not able to access when group defined in "valid users" parameters. below are the steps i performed. In smb.conf workgroup = QASLABS password server =... (3 Replies)
Discussion started by: sunnysthakur
3 Replies

7. Red Hat

Samba share problem in Linux 6.4

Hi , In samba i have shared my home directory, but its showing as a printer. Not able to share data. $ smbclient -L 192.168.122.1 Enter priyank's password: Domain= OS= Server= Sharename Type Comment --------- ---- ------- shared_priyank Printer ... (3 Replies)
Discussion started by: Priy
3 Replies

8. UNIX for Beginners Questions & Answers

Samba Share access from windows

Hello, I want to connect to two samba shares both on the same Linux box but each with a different username from a windows server 2008. I created 2 gpos to connect and I can connect to the shares individually via net use command, but once I entered credentials for one of the shares, it seems I... (1 Reply)
Discussion started by: zaineyma
1 Replies

9. Red Hat

Samba share - currently not working

Long running samba share. Never have any problems, Suddenly started asking windows users for password - which doesnt work. Tried to manually reset smb password and manually map - still wrong password. Restart samba? (2 Replies)
Discussion started by: psychocandy
2 Replies

10. UNIX for Advanced & Expert Users

Mounting a samba share

Hi, I need to mount a directory from a Windows server to a CentOS box. The Windows server used is Windows Server 2003, and the path to the directory that I want to mount on CentOS is C:\Tomcat6\webapps\NASApp\logs. I am not sure of the correct way to mount this on CentOS, as most of the... (2 Replies)
Discussion started by: anaigini45
2 Replies
TARGETS(5)						      BSD File Formats Manual							TARGETS(5)

NAME
targets -- configuration file for iSCSI targets SYNOPSIS
targets DESCRIPTION
The targets file describes the iSCSI storage which is presented to iSCSI initiators by the iscsi-target(8) service. A description of the iSCSI protocol can be found in Internet Small Computer Systems Interface RFC 3720. Each line in the file (other than comment lines that begin with a '#') specifies an extent, a device (made up of extents or other devices), or a target to present to the initiator. Each definition, an extent, a device, and a target, is specified on a single whitespace delimited line. The extent definition specifies a piece of storage that will be used as storage, and presented to initiators. It is the basic definition for an iSCSI target. Each target must contain at least one extent definition. The first field in the definition is the extent name, which must begin with the word ``extent'' and be followed by a number. The next field is the file or NetBSD device which will be used as persistent storage. The next field is the offset (in bytes) of the start of the extent. This field is usually 0. The fourth field in the definition is the size of the extent. The basic unit is bytes, and the shorthand KB, MB, GB, and TB can be used for kilobytes (1024 bytes), megabytes (1024 kilobytes), gigabytes (1024 megabytes), and terabytes (1024 gigabytes) respectively. It is possible to use the word ``size'' to use the full size of the pre-existing regular file given in the extent name. The device definition specifies a LUN or device, and is made up of extents and other devices. It is possible to create hierarchies of devices using the device definition. The first field in the definition is the device name, which must begin with the word ``device'' and be followed by a number. The next field is the type of resilience that is to be provided by the device. For simple devices, RAID0 suffices. Greater resilience can be gained by using the RAID1 resilience field. Following the resilience field is a list of extents or other devices. Large devices can be created by using multiple RAID0 extents, in which case each extent will be concatenated. Resilient devices can be cre- ated by using multiple RAID1 devices or extents, in which case data will be written to each of the devices or extents in turn. If RAID1 resilience is used, all the extents or sub-devices must be the same size. Please note that RAID1 recovery is not yet supported by the iscsi-target(8) utility. An extent or sub-device may only be used once. The target definition specifies an iSCSI target, which is presented to the iSCSI initiator. Multiple targets can be specified. The first field in the definition is the target name, which must begin with either of the words ``target'' or ``lun'' and be followed by a number. Optionally, if a target is followed by an ``='' sign and some text, the text is taken to be that of the iSCSI Qualified Name of the target. This IQN is used by the initiator to connect to the appropriate target. The next field is a selector for whether the storage should be pre- sented as writable, or merely as read-only storage. The field of ``rw'' denotes read-write storage, whilst ``ro'' denotes read-only storage. The next field is the device or extent name that will be used as persistent storage for this target. The fourth field is a slash-notation netmask which will be used, during the discovery phase, to control the network addresses to which targets will be presented. The magic val- ues ``any'' and ``all'' will expand to be the same as ``0/0''. If an attempt is made to discover a target which is not allowed by the net- mask, a warning will be issued using syslog(3) to make administrators aware of this attempt. The administrator can still use tcp wrapper functionality, as found in hosts_access(5) and hosts.deny(5) to allow or deny discovery attempts from initiators as well as using the inbuilt netmask functionality. FILES
/etc/iscsi/targets the list of exported storage targets SEE ALSO
syslog(3), hosts.deny(5), hosts_access(5), iscsi-target(8) HISTORY
The targets file first appeared in NetBSD 4.0. BSD
December 18, 2007 BSD
All times are GMT -4. The time now is 11:56 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy