similar to: partition not found when remounting in RW mode

I have tried everything to compile a new kernel on my 7.2 base system. I have used 2.4.13-ac6 and 2.4.13 w/ ext3 patch. I have compiled with ext3 built-in and with ext3 as module (with the initrd). I have a SCSI system so I have done the previous variations with both SCSI support built-in and modular (with the initrd). The error I get is: Remounting root filesystem in read-write mode: mount: no

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I was a thread on the list archive from a few months ago, about a user who had added 'data=journal' in /etc/fstab. The system stopped working properly because the device couldn't be remounted rw after fsck ran - because ext3 wouldn't allow changing the journalling options on remount. I can understand that changing data=x in general

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

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

I've noticed that once I right click on my flash drive icon and umount it, in order to remount it I have to unplug it and then plug it back in. Is there a command that will accomplish the same task without the unplug and plug back in physics? Thanks. mhr

I was running solaris 10 6/06 with latest kernel patch on ultra 20 (x86) with two internal disks, the root with the OS (c1d0) as UFS and the userland data on c2d0s7 formatted as ZFS. An update made the system unusable and required reinstallation of the OS on c1d0 (solaris 6/06). I cannot figure out how to remount the second drive c2d0s7 which is formatted as ZFS. I have not created any ZFS

Hi Guys, I was looking at the code of ext3 file system and found some strange implementation there : Can someone please let me know the validity of below statements : 1. I found that it might also happen that journal is aborted but not re-mounted 2. Journal gets aborted but it might be possible to mount it in read-write mode. 3. Can we write some data on the partition where journal is

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)

Time Machine will enable ownership on the drive the first time it starts up. The first thing it does when it creates the backup directory is to enable ownership on the drive. I've seen this happen repeatedly (it's actually the easiest way I know of to enable ownership on drive). On 2018-04-03, at 4:05 AM, Dave Gordon via rsync <rsync at lists.samba.org> wrote: > On 20/03/18

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

Hi! Today I switched over to devfs. I'm on Debian unstable, installed devfsd, installed a kernel with devfs support and "devfs mount on boot". Reboot, devfs is being used. All over a sudden, dmesg reports: Linux version 2.4.21-ac1 (root@hummus) (gcc version 3.3 (Debian)) #1 Sun Jun 15 19:06:13 CEST 2003 ... kjournald starting. Commit interval 5 seconds EXT3-fs: mounted

I'm using the ext3-patched version of Linux 2.4.13 (the patch from Andrew Morton's UOW site). I compiled both ext3 and ext2 into the kernel. I've also done "tune2fs -j /dev/hda3" and changed /etc/fstab to ext3. However, when I boot up, the filesystem still gets mounted as ext2. I've been trying to figure out why for many days now.. any ideas? Here's my setup:

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

For some asynchronous threads, such as submit worker and cache worker, we limit their thread pool size when mounting. So we also need to do such things when remounting. Signed-off-by: Liu Bo <bo.li.liu@oracle.com> --- fs/btrfs/super.c | 13 ++++++++----- 1 files changed, 8 insertions(+), 5 deletions(-) diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c index 83d6f9f..a58e834 100644 ---

I successfully did my first FreeBSD upgrade yesterday after looking at the manual, and cross referencing with Googling and getting help from our network engineer here at CWU. Before the upgrade, running df showed: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s1a 507630 77662 389358 17% / devfs 1 1 0 100% /dev /dev/da0s1e

On 06/10/2013 01:41 PM, pr.G wrote: > On Mon, Jun 10, 2013 at 09:29:32AM +0400, свящ. Георгий Гольцов wrote: >> On Mon, Jun 10, 2013 at 09:07:08AM +0800, Gao feng wrote: >>> On 06/09/2013 08:14 PM, pr.G wrote: >>>> Hello. >>>> >>>> Is it possible to start container via libvirt_lxc without mounting /sys >>>> inside container?

Hey A wise man said to me that Hashing filters was my solution to rock the world, and making my life alot easier. When applying 4000 rules, the system had to check them all for match. But with hassing it would only require 1-2 checks. Even though when i had read the lartc on the subject i was no less that a question mark. If anyone have played with it, and have a working, logic configuration

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:

That doesn’t work too. :-( Last login: Mon Mar 19 19:18:16 on console iMac:~ andre$ mount /dev/disk0s2 on / (hfs, local, journaled) devfs on /dev (devfs, local, nobrowse) map -hosts on /net (autofs, nosuid, automounted, nobrowse) map auto_home on /home (autofs, automounted, nobrowse) /dev/disk2 on /Volumes/G-DRIVE Thunderbolt 3 (hfs, local, nodev, nosuid, journaled, noowners) iMac:~ andre$