similar to: root fs type in fstab

Our main NFS-server, running Debian Potato, died this morning whilst under quite heavy load - due to a runaway perl-script forking of some 200 instances of "/bin/cp" (the load was ~ 50). The server is running 2.2.19pre14 with ext3-0.0.6b. The server is running kernel-nfs. Assertion failure in journal_dirty_metadata() at transaction.c line 796: "bh->b_next_transaction ==

This is a 2.2.19 machine with ext3-0.0.7a and quota support running. The symptoms are a particular NFS export hangs (for linux clients but not Solaris clients?) the local filesystem gives the following: EXT3-fs warning (device sd(8,49)): ext3_free_blocks: bit already cleared for block 2213 EXT3-fs error (device sd(8,49)): ext3_free_blocks: Freeing blocks not in datazone - block = 1563120916,

Hi all, I want to setup a RAID storage system, where i have two systems connected to it. the filesystems are mapped out to both connectors. I want the master host mount them read write, and the slave read only. in my fstab on the slave I have a line like the following: /dev/sdb1 /mount ext3 acl,noauto,user_xattr,nosuid,ro 0 0 so in man 5 fstab, it is written, that when the 6. field

For some time now I have been puzzled as to why certain portions of my system boot were quite slow -- but only after journal recoveries. I was fearing that there was some ugly interaction between the recovery and the use of the journal shortly afterward but alas that is not the case. So just in case anybody else is seeing this problem and decides to try to hunt it down, let me save you some

This patch contains the following possible cleanups: - make needlessly global functions static - #if 0 the following unused global functions: - journal.c: __journal_internal_check - journal.c: journal_ack_err - remove the following write-only global variable: - journal.c: current_journal - remove the following unneeded EXPORT_SYMBOL's: - journal.c: journal_check_used_features -

This patch contains the following cleanups: - make needlessly global functions static - journal.c: remove the unused global function __journal_internal_check and move the check to journal_init - remove the following write-only global variable: - journal.c: current_journal - remove the following unneeded EXPORT_SYMBOL: - journal.c: journal_recover Signed-off-by: Adrian Bunk

This patch contains the following possible cleanups: - make needlessly global functions static - journal.c: remove the unused global function __journal_internal_check and move the check to journal_init - remove the following write-only global variable: - journal.c: current_journal - remove the following unneeded EXPORT_SYMBOL's: - journal.c: journal_check_used_features -

I made some tests to see how ext3 reiserfs 3.6 and jfs survive disk errors. The test is simple: format a partition, copy the kernel source, unmount and and do ?dd if=/dev/zero of=/dev/hdd bs=512 count=100000 seek=30000? to simulate a disk surface damage and then run fsck. seek=30000 ? this must be the second half of journal in reiserfs and ext3, for jfs I don't know Result: jfs: ---- total

I have a CentOS 5 machine with an external 500G USB disk, formatted with JFS. How do I get this to mount automatically at boot time? If I add to /etc/fstab: /dev/sdb1 /var/video jfs defaults 1 2 fsck.jfs complains at boot time: Error: Cannot open device /dev/sdb1 Usage: fsck.jfs ... ... Give root password for maintenance ... If I log in with the root password, /dev/sdb1 is present, and I

Hello I run the latest kernel from centosplus and use a JFS partition. Even though the jfs tools are installed, when the server crashes, it doesn't run fsck.jfs automatically when at boot time it detects that the partition is corrupted I have to run fsck.jfs manually and mount the drive. Is there a way to make fsck.jfs run automatically if required ? (I recently moved from Fedora to

I updated my kernel from 0.0.3d to 0.0.3e using the "d-e" patch in the 0.0.3e tarball. When I try to boot the new kernel on a machine with an ext3 root filesystem I am getting the message: JFS: Unrecognised features on journal Does this sound feasible or even somewhat expected? Is there any interest in me doing some debugging of this? Is there any way to deal with this without

Hi list, Something went wrong this morning and we have a node ( #0 ) reboot. Something blocked the NFS access from both nodes, one rebooted and the another we restarted the nfsd and it brought him back. Looking at node #0 - the one that rebooted - logs everything seems normal, but looking at the othere node dmesg's we saw this messages: First the o2net detected that node #0 was dead: (It

Hi all, ext3-0.0.5c is now up at: ftp.uk.linux.org:/pub/linux/sct/fs/jfs/ and ftp.*.kernel.org:/pub/linux/kernel/people/sct/ext3/ The most important part of this release is the e2fsprogs: e2fsck now supports the journal changes for metadata-only journaling. Ted, I've changed around the use of jfs* include files in e2fsprogs quite heavily here. In each build directory --- the lib/ext2fs

On 10/26/2017 08:01 PM, Akemi Yagi wrote: > On Thu, Oct 26, 2017 at 4:17 PM, H <agents at meddatainc.com> wrote: > >> On October 26, 2017 6:31:04 PM EDT, Akemi Yagi <amyagi at gmail.com> wrote: >>> On Thu, Oct 26, 2017 at 3:11 PM, H <agents at meddatainc.com> wrote: >>> >>>> On 04/18/2017 12:54 PM, H wrote: >>>>> A couple

Hi, ext3-0.0.5d.tar.gz is now up on ftp.uk.linux.org:/pub/linux/sct/fs/jfs/ and ftp.*.kernel.org:/pub/linux/kernel/people/sct/ext3/ as patches against 2.2.18. This only contains the kernel bits: we're in the process of syncing up on some e2fsprogs so I'll do another release shortly once we've got all of the pending changes for the user-mode tools assembled. This release is mostly

On 04/18/2017 12:54 PM, H wrote: > A? couple of days ago I submitted a request to ElRepo and kmod-jfs is now available for CentOS 7 as well. > > On 04/12/2017 12:58 AM, H wrote: >> Thank you, installed it and it worked fine. Now I am looking for the same for CentOS 7... It did not look like you have that in your repository? >> >> >> On 3/13/2017 1:09 PM, Nux!

On October 26, 2017 6:31:04 PM EDT, Akemi Yagi <amyagi at gmail.com> wrote: >On Thu, Oct 26, 2017 at 3:11 PM, H <agents at meddatainc.com> wrote: > >> On 04/18/2017 12:54 PM, H wrote: >> > A couple of days ago I submitted a request to ElRepo and kmod-jfs >is >> now available for CentOS 7 as well. >> > >> >> Did not have a need to

Hi, we have CentOS ftp server (vsftpd) which has a lot of users who are writing and reading a lot of small files from/into its own accounts (and other servers - using samba client - are reading these files and putting them into outside database). Since this server is under heavy load its availability is important. >From time to time we "crash" this server (don't ask why ...) but

Hello. I have installed the ext3 file system on a test system, and sometimes I have a problem: I get an assert from within jbd-kernel.c, and whatever prgram was writing to the disk when this happens is unable to continue. The system is a server I built, which I named "dax". It is running Debian unstable, and I updated it to all the latest packages in Debian unstable as of today.

Hello all, I'm relatively new to CentOS, but I've been using linux as my main operating system on both the desktop and server ends for the past 4 years. I currently have a PIII server with two 160GB IDE hard drives in it, in a virtual RAID 1 array. At the time of installation, the only FS choices for the largest partition, 120GB, were ext2 and ext3. I chose ext3, but now am wishing