similar to: mount -o remount /mnt/samba creates duplicate mount

I'm having issues trying to remount any shares using samba. Super Short version mount -o remount /some_windows_share creates a duplicate mount instead of properly remounting. Full details... I have many shares served off of NT4 boxes, mounted via samba on a linux box (RHEL 4). Since long dormant (>12 hour) shares from one server in particular always have problems for a few seconds when

Hi all, We've having an issue at the moment where an iSCSI connection was temporarily lost on a few VMs running CentOS 6 on ESXi. The problem is, now that the iSCSI connection has returned, we are not able to remount the drive. At first the drive is read-only, so I tried '*mount -o remount,rw*' which didn't work (still read-only), so then I tried a '*umount*' (which

I'm having issues trying to remount any shares using samba. Super Short version mount -o remount /some_windows_share creates a duplicate mount instead of properly remounting. Full details... I have many shares served off of NT4 boxes, mounted via samba on a linux box (RHEL 4). Since long dormant (>12 hour) shares from one server in particular always have problems for a few seconds when

Hi All. I have a setup in which I have two servers serving nfs share. The nfs service is made highly available with pacemaker. When the primary server goes down the secondary starts nfs service. Service IP is floating between servers but they have NO "shared" storage/filesystem so NFS state/connection information in case of failover is lost. I have two clients. When the failover from

Any clue on dmesg? I'd remove de disk and rescan... El jue., 5 de marzo de 2015 a las 7:40, Kyle Thorne (< kthorne at staff.ventraip.com>) escribi?: > Hi all, > > We've having an issue at the moment where an iSCSI connection was > temporarily lost on a few VMs running CentOS 6 on ESXi. > > The problem is, now that the iSCSI connection has returned, we are not able

I'm having a problem where NT users are rebooting (go figure) their machines, and breaking mounts from that machine. What I'd like to do is either configure my SAMBA stuff correctly to recover these mounts automatically, or write a script to umount/mount them for me when they fail. The problem I'm having it, how do I tell that a mount has died so I can remount it? I'd assume

The most recent message is: [3108269.919256] sd 2:0:1:0: timing out command, waited 1080s [3108269.919528] sd 2:0:1:0: [sdb] Unhandled error code [3108269.919535] sd 2:0:1:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_OK [3108269.919540] sd 2:0:1:0: [sdb] CDB: Read(10): 28 00 00 01 21 47 00 00 08 00 [3108269.919586] EXT4-fs error (device sdb1): ext4_find_entry: reading directory #2 offset 0

Following the announcement on lkml, I have started using ext3 on one of my servers. Since the server in question is a farily security-sensitive box, my /usr partition is mounted read only except when I remount rw to install packages. I converted this partition to run ext3 with the mount options "nodev,ro,data=writeback,defaults" figuring that when I need to install new packages etc,

Hi all, I was recently poking more into the inode64 mount option for XFS filesystems. I seem to recall a comment that you could remount a filesystem with inode64, but then a colleague ran into issues where he did that but was still out of inodes. So, I did more research, and found this posting to the XFS list: http://oss.sgi.com/archives/xfs/2008-05/msg01409.html So for people checking the

Unfortunately, this is another "I don''t yet know ruby" question, but I''m hoping that someone can help me out. I''ve just tried to write some mount options via puppet and I noticed that, while fstab is written, the managed mounts are not remounted to effect the stated changes. For instance: Original - /home, options: rw Puppet - /home, options: rw,acl

Hi, every so often (cannot determine when it occurs at this time), the VM remount in read only the host partition (/srv here). Is it a bug? A misconfiguration? My config: <filesystem type='mount' accessmode='passthrough'> <source dir='/srv/lxc/lib/vprobe10/rootfs'/> <target dir='/'/> </filesystem> -- Sebastien Douche

In support of the recently added capability to remount with lzo compression, provide a helper function to check the compression INCOMPAT flags when remounting with lzo compression, and set the flags if necessary. Also, implement the new helper function when defragmenting with explicit lzo compression and when setting the default subvolume. Signed-off-by: Mitch Harder

In btrfs if we mount with "compress" we have no way to disable compressing by remounting (mount -o remount /mnt/btrfs), only by unmounting and mounting without "compress". This patch adds "nocompress" mount option which can be used to remount the filesystem without compression: # mount -o remount,nocompress /mnt/btrfs This option is usefull in cases when we have a

Dear all, I followed the instructions found on http://www.zip.com.au/~akpm/linux/ext3/ext3-usage.html to convert / on several of my boxes to ext3. Strange to me, on some boxes it perfectly worked while on others it didn't. One of the differences found is that on the ok-boxes mount reports: /dev/hda3 on / type ext3 (rw,errors=remount-ro) /* Settings: cat /etc/fstab /dev/hda3 / ext3

How does one go about adding a machine account, or even a normal samba account, on a Samba PDC with LDAP back end? I wanted to avoid using something like smbldap-useradd, because I want to actually understand what's going on. I'm assuming it's just some sort of small ldif to add, like I would for adding user, am I wrong? Thanks, Kyle

Is there some automated system to import windows accounts into a samba or a samba ldap situation? I've got a few hundred users on an NT domain, and I'd like to migrate them sometime before the last piece of hardware supported by NT4 rusts. Right now several linux based samba servers are doing all of the heavy lifting (shared files printers etc), but they are all looking at the domain

Hi all, I am testing new kernel on a mips machine (64 bits for kernel, 32 bits userland) and I found a problem when mounting the root file system. It is an ext3 file system that is correctly mounted as read only. While booting the system remount the file system as read/write and keep starting all daemons. Moving from 2.6.26 to 2.6.30 kernel, I get this error while remounting the file system

I''m trying to get a new file server managed by puppet from day 1, at least as much as possible. At the moment, though, there''s two issues I''m running into: 1. fstab should have entries for my comically-large RAID, but doesn''t. 2. each puppet run appears to remount the RAID, even when no rules in the manifest change. I suspect the issue may be in parsing

What's the proper way to unmounts and remount a glusterfs? Tried -o remount, no luck, ended up having to umount -f it, and now I can't reconnect it...always ends up with a 'transport end not connected' error no matter what I use (mount.glusterfs, glusterfs, mount -t glusterfs, mount -a, etc) Even after I umounted it, it's also still showing in 'mount' ...so confused!

I have several filesystems created from the pool; and some mountpoints are inside the others, e.g.: # zfs list NAME USED AVAIL REFER MOUNTPOINT nfsv4pool 15.5M 33.5G 98.5K /nfsv4pool nfsv4pool/KRB5_FS 1.87M 33.5G 1.87M /export/test/KRB5_FS nfsv4pool/NOSPC_FS 3.01M 0 3.01M /export/test/NoSPC_FS nfsv4pool/NOTSHARE_FS 105K 33.5G 105K