10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
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
2. Red Hat
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
3. UNIX for Beginners Questions & Answers
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
4. Red Hat
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
5. Red Hat
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
6. Solaris
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
7. UNIX for Advanced & Expert Users
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
8. Linux
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
9. Linux
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
10. UNIX for Dummies Questions & Answers
thank u very much, (1 Reply)
Discussion started by: coralsea
1 Replies
raidtab(5) File Formats Manual raidtab(5)
NAME
raidtab - configuration file for md (RAID) devices
DESCRIPTION
/etc/raidtab is the default configuration file for the raid tools (raidstart and company). It defines how RAID devices are configured on a
system.
FORMAT
/etc/raidtab has multiple sections, one for each md device which is being configured. Each section begins with the raiddev keyword. The
order of items in the file is important. Later raiddev entries can use earlier ones (which allows RAID-10, for example), and the parsing
code isn't overly bright, so be sure to follow the ordering in this man page for best results.
Here's a sample md configuration file:
#
# sample raiddev configuration file
# 'old' RAID0 array created with mdtools.
#
raiddev /dev/md0
raid-level 0
nr-raid-disks 2
persistent-superblock 0
chunk-size 8
device /dev/hda1
raid-disk 0
device /dev/hdb1
raid-disk 1
raiddev /dev/md1
raid-level 5
nr-raid-disks 3
nr-spare-disks 1
persistent-superblock 1
parity-algorithm left-symmetric
device /dev/sda1
raid-disk 0
device /dev/sdb1
raid-disk 1
device /dev/sdc1
raid-disk 2
device /dev/sdd1
spare-disk 0
Here is more information on the directives which are in raid configuration files; the options are listen in this file in the same order
they should appear in the actual configuration file.
raiddev device
This introduces the configuration section for the stated device.
nr-raid-disks count
Number of raid devices in the array; there should be count raid-disk entries later in the file. (current maximum limit for RAID
devices -including spares- is 12 disks. This limit is already extended to 256 disks in experimental patches.)
nr-spare-disks count
Number of spare devices in the array; there should be count spare-disk entries later in the file. Spare disks may only be used with
RAID4 and RAID5, and allow the kernel to automatically build new RAID disks as needed. It is also possible to add/remove spares run-
time via raidhotadd/raidhotremove, care has to be taken that the /etc/raidtab configuration exactly follows the actual configuration
of the array. (raidhotadd/raidhotremove does not change the configuration file)
persistent-superblock 0/1
newly created RAID arrays should use a persistent superblock. A persistent superblock is a small disk area allocated at the end of
each RAID device, this helps the kernel to safely detect RAID devices even if disks have been moved between SCSI controllers. It
can be used for RAID0/LINEAR arrays too, to protect against accidental disk mixups. (the kernel will either correctly reorder disks,
or will refuse to start up an array if something has happened to any member disk. Of course for the 'fail-safe' RAID variants
(RAID1/RAID5) spares are activated if any disk fails.)
Every member disk/partition/device has a superblock, which carries all information necessary to start up the whole array. (for
autodetection to work all the 'member' RAID partitions should be marked type 0xfd via fdisk) The superblock is not visible in the
final RAID array and cannot be destroyed accidentally through usage of the md device files, all RAID data content is available for
filesystem use.
parity-algorithm which
The parity-algorithm to use with RAID5. It must be one of left-asymmetric, right-asymmetric, left-symmetric, or right-symmetric.
left-symmetric is the one that offers maximum performance on typical disks with rotating platters.
chunk-size size
Sets the stripe size to size kilobytes. Has to be a power of 2 and has a compilation-time maximum of 4M. (MAX_CHUNK_SIZE in the ker-
nel driver) typical values are anything from 4k to 128k, the best value should be determined by experimenting on a given array, alot
depends on the SCSI and disk configuration.
device devpath
Adds the device devpath to the list of devices which comprise the raid system. Note that this command must be followed by one of
raid-disk, spare-disk, or parity-disk. Also note that it's possible to recursively define RAID arrays, ie. to set up a RAID5 array
of RAID5 arrays. (thus achieving two-disk failure protection, at the price of more disk space spent on RAID5 checksum blocks)
raid-disk index
The most recently defined device is inserted at position index in the raid array.
spare-disk index
The most recently defined device is inserted at position index in the spare disk array.
parity-disk index
The most recently defined device is moved to the end of the raid array, which forces it to be used for parity.
failed-disk index
The most recently defined device is inserted at position index in the raid array as a failed device. This allows you to create raid
1/4/5 devices in degraded mode - useful for installation. Don't use the smallest device in an array for this, put this after the
raid-disk definitions!
NOTES
The raidtools are derived from the md-tools and raidtools packages, which were originally written by Marc Zyngier, Miguel de Icaza, Gadi
Oxman, Bradley Ward Allen, and Ingo Molnar.
SEE ALSO
raidstart(8), raid0run(8), mkraid(8), raidstop(8)
raidtab(5)