search for: remounts

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

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,

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, I'm running kernel 2.6.8-15, lvm2 v2.01.04-5 and acl v2.2.23-1 on a Sunblade 100 (sparc). In a few months we have experienced for several times that an ext3 filesystem is remounted as read-only (this is due to the option "errors=remount-ro" in /etc/fstab). Sometimes there is no error in log files but sometimes we see: kernel: init_special_inode: bogus i_mode (3016) kernel:

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 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

While compiling two kernels and untarring a third, my root fs was remounted r/w and I got the following in dmesg (kernel 2.4.19-pre9): EXT3-fs error (device ide0(3,2)) in ext3_new_inode: error 28 Aborting journal on device ide0(3,2). ext3_abort called EXT3-fs abort (device ide0(3,2)): ext3_journal_start: Detected aborted journal. Remounting filesystem read-only Remounting filesystem read-only

On a 2.4.17 (MontaVista 2.1) kernel using ext3, I recently starting seeing the error EXT3-fs error (device ide1(22,1)) in start_transaction: Readonly filesystem EXT3-fs error (device ide1(22,1)) in ext3_delete_inode: Readonly filesystem on a file system within 10-20 seconds after remounting it r/o. Apparemtly a write is being deferred past the remount point and then runs into problems when it is

Hi all, I have some AVC in the logs and wonder how to resolve this: Under EL8 (enforcing SElinux) I have /var/lib/php/session mounted as tmpfs. # tail -1 /etc/fstab tmpfs /var/lib/php/session tmpfs defaults,noatime,mode=770,gid=apache,size=16777216,context="system_u:object_r:httpd_var_run_t:s0" 0 0 # df -a |grep php tmpfs 16384 0 16384 0%

This is a repost, since I'd really like to get some info about whats going on. when using, "mount -o remount" on an linux box, I get a duplicate mount instead of a proper remount. /proc/mounts backs me up: the system really does have multiple mounts in the same place, of the same drive. The version of samba installed is 3.0.10, the distro is RedHat Enterprise Linux 4, kernel is

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

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

Hi, Apologies in advance for any breaches of netiquette, I couldn't find any guidelines about submission to this forum but I'd be grateful for your help on something. My /boot filesystem is being remounted shortly after start-up as read-only. I get the following messages... journal_bmap_Ra7a5f568: journal block not found at offset 12 on ide0(3,1) Aborting journal on device ide0(3,1)

I am trying to track down a problem I reported on the list last week and discovered a new problem during my testing. If you have a four node setup with replicate/distribute and one of the nodes has a filesystem failure, the operating system will typically remount the filesystem read only. When this happens, the glusterfsd is still running on the failed machine, but i doesn't seem to

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

Can anyone comment on whether or not it is possible to successfully disable the journal of an ext3 root file system prior to reboot? My application is to try and make sure there is no journal prior to installing and rebooting into a system which does not support ext3. I know that as long as the root is cleanly remounted r/o with no journal updates pending, this will be compatible. I'm

Suppose I have the latest and greatest e2fsprogs. >From reading the docs I understand that 1) boot ext3, clean umount - you can remount ext3 or ext2 2) boot ext3, unclean umount - you can remount ext3 - you can e2fsck and remount ext2 Does this mean that normal linux init script e2fsck will do it, in case fstab says ext2? Or you should make sure to run e2fsck by hand with -f? 3) boot

If I have an operation, such as an RPM install, and I have certain mounts that are read-only, how should I go about making sure that they are read write prior to an update? For example: 1. Re-mount file systems as read write. 2. Perform RPM updates 3. Re-re-mount file systems as read only. I got to thinking about this when I saw the post about automatic remounting after changing mount options.

Hi, I have a box with / and /home being subvolumes from the same btrfs filesystem. /etc/fstab: UUID=c0686... / btrfs subvol=root,x-systemd.device-timeout=0 1 1 UUID=c0686... /home btrfs subvol=home,x-systemd.device-timeout=0 1 1 ... / is initially mounted readonly by the initramfs, and then after switching to the real system, /home is attempted to be mounted in parallel with /

Hi, I installed RH 7.2 with the original kernel and decided to use ext3 as the fs. All partitions are now ext3. This is working fine as long as I'm using the original kernels. Now I wanted to compile my own kernel (2.4.13), but there seems to be a problem. When it it tries to remount my root partition / in RW, I get an error message that the partition cannot be found. When I reboot using the