Please answer the question asked by Peasant about did you run:
Quote:
Originally Posted by Peasant
Lets just make this clear for the sake of argument.
So, you create a /dev/md0 from /dev/sdc /dev/sdb disks.
You mount it via mount command and add into /etc/fstab.
After reboot (all disks are inside), everything works as expected (mounted and healty).
You poweroff the box, and remove one of the disks from array.
Booting up everything is fine, except lacking one disk you removed.
After you poweroff and replug the drive, power on, there should be still one disk in the md setup. The one you didn't touch should still be part of md device.
Is this correct ?
Point being, if you unplug the drive, that drive is not considired part of array anymore.
When you plug it back, it will not magically rebuild, this has to be done by hand.
And of course, if you plug the other one out, and leave the first one in, you will not have a working md array.
Regards
Peasant.
You are right.
I added it to md0 manually, thats not a problem. Problem is why my data from /mnt/raid is not accessible and i cant read it when i unplug one of the 2 devices?
Thats strange from me, i cant figure out.
I added a folder in array in which i have mounted /dev/md0.
so i have a folder
/mnt/raid/test
and inside test some files.
I cant access it and all is fine. When I unplug disk when machine is running(or not, its the same result), i cant read from that test folder.
Input output error gives me.
But when I unplug another disk, it is working just fine.
Thats what bothers me.
Idea behind all this is to have a shared folder and prevention of data loss. If that disk fails i cannot access to that files. Thats the problem
Last edited by tomislav91; 08-31-2018 at 10:12 AM..
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)
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)
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)
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)
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)
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)
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)
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)
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
LEARN ABOUT FREEBSD
mount.conf
MOUNT.CONF(8) BSD System Manager's Manual MOUNT.CONF(8)NAME
mount.conf -- root file system mount configuration file
SYNOPSIS
/.mount.conf
DESCRIPTION
During the bootup process, the FreeBSD kernel will try to mount the root file system using the logic in the vfs_mountroot() function in
src/sys/kern/vfs_mountroot.c. The root mount logic can be described as follows:
1. The kernel will synthesize in memory a config file with default directives for mounting the root file system. The logic for this is in
vfs_mountroot_conf0().
2. The kernel will first mount devfs(8) as the root file system.
3. Next, the kernel will parse the in-memory config file created in step 1 and try to mount the actual root file system. See FILE FORMAT
for the format of the config file.
4. When the actual root file system is mounted, devfs will be re-mounted on the /dev directory.
5. If a /.mount.conf file does not exist in the root file system which was just mounted, the root mount logic stops here.
6. If a /.mount.conf file exists in the root file system which was just mounted, this file will be parsed, and the kernel will use this new
config file to try to re-mount the root file system. See FILE FORMAT for the format of the config file.
7. If the new root file system has a /.mount directory, the old root file system will be re-mounted on /.mount.
8. The root mount logic will go back to step 4.
The root mount logic is recursive, and step 8 will be repeated as long as each new root file system which is mounted has a /.mount.conf file.
FILE FORMAT
The kernel parses each line in .mount.conf and then tries to perform the action specified on that line as soon as it is parsed.
# A line beginning with a # is a comment and is ignored.
{FS}:{MOUNTPOINT} {OPTIONS}
The kernel will try to mount this in an operation equivalent to:
mount -t {FS} -o {OPTIONS} {MOUNTPOINT} /
If this is successfully mounted, further lines in .mount.conf are ignored. If all lines in .mount.conf have been processed and
no root file system has been successfully mounted, then the action specified by .onfail is performed.
.ask When the kernel processes this line, a mountroot> command-line prompt is displayed. At this prompt, the operator can enter the
the root mount.
.md file Create a memory backed md(4) virtual disk, using file as the backing store.
.onfail [panic|reboot|retry|continue]
If after parsing all the lines in .mount.conf the kernel is unable to mount a root file system, the .onfail directive tells the
kernel what action to perform.
.timeout N Before trying to mount a root file system, if the root mount device does not exist, wait at most N seconds for the device to
appear before trying to mount it. If .timeout is not specified, the default timeout is 3 seconds.
EXAMPLES
The following example .mount.conf will direct the kernel to try mounting the root file system first as an ISO CD9660 file system on /dev/cd0,
then if that does not work, as an ISO CD9660 file system on /dev/acd0, and then if that does not work, as a UFS file system on /dev/ada0s1a.
If that does not work, a mountroot> command-line prompt will be displayed where the operator can manually enter the root file system to
mount. Finally if that does not work, the kernel will panic.
.onfail panic
.timeout 3
cd9660:/dev/cd0 ro
.timeout 0
cd9660:/dev/acd0 ro
.timeout 3
ufs:/dev/ada0s1a
.ask
The following example .mount.conf will direct the kernel to create a md(4) memory disk attached to the file /data/OS-1.0.iso and then mount
the ISO CD9660 file system on the md device which was just created. The last line is a comment which is ignored.
.timeout 3
.md /data/OS-1.0.iso
cd9600:/dev/md# ro
# Can also use cd9660:/dev/md0 ro
The following example .mount.conf will direct the kernel to create a md(4) memory disk attached to the file /data/base.ufs.uzip and then
mount the UFS file system on the md uzip device which was just created by the geom_uzip(4) driver.
.md /data/base.ufs.uzip
ufs:/dev/md#.uzip ro
# Can also use ufs:/dev/md0.uzip ro
The following example .mount.conf will direct the kernel to do a unionfs mount on a directory /jail/freebsd-8-stable which has a chroot(2)
environment.
.timeout 3
unionfs:/jail/freebsd-8-stable
NOTES
For each root file system which is mounted, a /dev directory must exist so that the root mount logic can properly re-mount devfs(8). If this
directory does not exist, the system may hang during the bootup process.
SEE ALSO nmount(2), md(4), boot.config(5), fstab(5), boot(8), loader(8), mount(8)HISTORY
The mount.conf file first appeared in FreeBSD 9.0.
AUTHORS
The root mount logic in the FreeBSD kernel which parses /.mount.conf was written by Marcel Moolenaar <marcel@FreeBSD.org>. This man page was
written by Craig Rodrigues <rodrigc@FreeBSD.org>.
BSD July 7, 2013 BSD