similar to: Fstab mounting error

Hi all, Bit of a sticky situation - we use rsync to mirror files from a remote staging server to our development server (both on Linux). The mirroring works fine, however, while the rsync process is running, our apache service on the destination system can't access the files. Is rsync locking the destination file system while it checks the files or something? Anyone got any idea how I

Hi list, Having a problem connecting to a Samba server under Fedora Core 6. Every time I try to connect, even from localhost, I get the message NT_STATUS_BAD_NETWORK_NAME. Samba config was done in the Redhat samba configuration tool (gnome). I can connect with smbclient -L illuminatus -U <username> and get a list of the shares. However when I try to connect with smbclient -U

Hi, I have a dilemma - here's some background: Up until recently, a series of local scripts that run on our network ran on a Mac OS X box. I would like to migrate these scripts to a Fedora Core 4 box (for better perl, ruby,and pythoiin support), however, the scripts use directories in the Appleshare network. I have the /Volumes directory, in which OSX mounts the shares, shared via Windows

I apologize because I know that this has surely been dealt with and documented before, but I cannot find it anywhere on the samba website, nor did a google search produce anything. For future reference, some type of advanced search option for the mailing list archives would be great. I tried the old google "error" "site:site.to.search" and it didn't find anything

On Tuesday, 6 December 2016 09:46:25 CET Richard W.M. Jones wrote: > For example, converts "///usr//local//" -> "/usr/local". > --- > src/inspect-fs-unix.c | 52 +++++++++++++++++++++++++++++++++++++++++++++++++++ > 1 file changed, 52 insertions(+) > > diff --git a/src/inspect-fs-unix.c b/src/inspect-fs-unix.c > index a1a757c..0fea9c8 100644 > ---

For example, converts "///usr//local//" -> "/usr/local". --- src/inspect-fs-unix.c | 52 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 52 insertions(+) diff --git a/src/inspect-fs-unix.c b/src/inspect-fs-unix.c index a1a757c..0fea9c8 100644 --- a/src/inspect-fs-unix.c +++ b/src/inspect-fs-unix.c @@ -89,6 +89,7 @@ static char *resolve_fstab_device

I am using CENTOS 5 and I am stuck where I have to repair my boot loader and all of the files are read only so I cannot fix them. How do I get around this? Thanks Chuck -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20070907/a7d2c2df/attachment.html>

//winserver/winshare /linuxdir smbfs username=username,password=password, this line doesn't work for me in fstab in CentOS 5 to mount a Windows share, it works in other versions of RH. Any Ideas? Will using Windows NFS server/client (some reading required) work better than Samba?

Hi again! I would like to add an ext3 partition (eg. /dev/md11) with its external journal (on /dev/md21) to /etc/fstab in order to have it mounted while system-startup. Do I have to specify the external journal device in fstab or does the partition find its journal device by itself? If the first, ho should I specify it? I created the journal with mke2fs /dev/md22 -O journal_dev and the ext3

That seems to be the indication given by this webpage http://www.zip.com.au/~akpm/linux/ext3/ext3-usage.html However, default install of Redhat 7.2 setsup fs_passno(6th field of /etc/fstab) as 2 which asks you if you want to run fsck after an unclean shutdown The question is, is fsck required after an unclean shutdown or should one just rely on journal replay. What does fsck do when it sees an

For some odd reason, fsck has suddenly become confused about what "auto" means after I changed the root to ext3 and everything in fstab to auto. This is happening on a Redhat Pentium III box running 2.4.9 and I also installed just recently util-linux 2.11l and glibc 2.2.4. fsck is 1.2.5 as indicated below. fsck 1.25 (20-Sep-2001) Checking all file systems. Could not determine

[This email is either empty or too large to be displayed at this time]

/etc/fstab: //machine_name/SAN /mnt/SAN cifs defaults 0 0 [root at machine_name SAN]# mount -a Password: mount error 13 = Permission denied Problem is there is no password to the smb server. Why am I getting a password prompt when the share has full RW access and all access is granted on the share? Note, though the share is fully visable and accessable and writeable by just browsing the

Hi again, I''m trying to manage mount options in /etc/fstab with Augeas but can''t figure out how to add more than one option. augeas { "/etc/fstab": context => "/files/etc/fstab", changes => [ ''set *[file = "/tmp"]/opt nosuid'',

All, I wanted to pass on experience that I have trying to get GlusterFS to automount on RedHat 5.5. The documentation for /etc/fstab (http://gluster.com/community/documentation/index.php/Mounting_a_GlusterFS_Volume) doesn't quite work. I have two servers 192.168.104.151 and 192.168.104.152. Both are running GlusterD and both offer one of the bricks for the volume. Both mount also the

Hi all, I am using a single volume across two devices sdb7 and sda1, initially created on sdb7, and added sda1 using btrfs-vol later. The fstab entry: /dev/disk/by-id/scsi-SATA_ST31000333AS_9TE12DSC-part7 /mnt/btrfs btrfs defaults 1 2 Now after boot I get: ---- device fsid c4822885057410c-d2d65a83c2f15fb4 devid 1 transid 73034 /dev/sdb7 btrfs: failed to read chunk tree on sdb7 ---- So I have

I have the following as the last line of my /etc/fstab file on a computer running CentOS6.4.. UUID=3b550884-8d05-41a5-a205-17b6d7269dd1 /mnt ext3 rw,suid,dev,exec,noauto,nouser,async 0 2 The UUID refers to an ext3 partition of a removable USB drive. If the USB drive is not plugged into the computer the computer will not boot. It seems that this is the incorrect behavior since

There is a specific example of this on the puppet Wiki iirc. Or very similar . Regards. ----Messaggio originale---- Da: Adam Heinz Inviato: 08/06/2011, 16:17 A: puppet-users@googlegroups.com Oggetto: Re: [Puppet Users] Managing /etc/fstab options with augeas On Thu, Jun 2, 2011 at 4:22 AM, Giovanni Bordello <gibo@gentlemail.com> wrote: > I''m trying to manage mount options in

RHEL 6.5 Puppet 3.7.1 puppetlabs-stdlib-4.3.2 Local hardening guidelines say that /usr/local and /var/log/audit have to be separate partitions. OK, so I make "mount" resources. Now the problem: The order of the mount points in /etc/fstab makes a difference. I had /usr/local before /usr, and at boot, the mount of /usr/local failed because the mount point did not (yet) exist. So I need

I have extended attributes in my fstab set with the following options: /dv/md0 /mnt/raid ext4 auto,errors=remount-ro,user_xattr 0 2 Aside from the "user_xattr" flag, do I have to set any other options to save extended attribute or file permissions information correctly to my share? I am running Samba 3.4.7 under Ubuntu 10.04 server. Derek