similar to: question about exact behaviour with data=ordered.

>From nfs-admin@lists.sourceforge.net Wed Jan 31 09:21:55 2001 >Return-Path: <nfs-admin@lists.sourceforge.net> Received: from usw-sf-list1.sourceforge.net (usw-outbound.sourceforge.net [216.136.171.194]) by gateway.camelot.jp (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id JAA03106 for <jareth@camelot.co.jp>; Wed, 31 Jan 2001 09:21:53 +0900 X-Authentication-Warning:

On Sunday March 16, gilbertd@treblig.org wrote: > Hi, > I've just built an 800GB RAID5 array and built an ext3 file system > on it; on trying to copy data off the 200GB RAID it is replacing I'm > starting to see errors of the form: > > kernel: EXT3-fs error (device md(9,2)): ext3_new_block: Allocating block in > system zone - block = 140509185 > > and >

----- Forwarded message from Neil Brown <neilb@cse.unsw.edu.au> ----- On Wednesday September 19, mfedyk@matchmail.com wrote: > On Tue, Sep 18, 2001 at 09:08:32PM +1000, Neil Brown wrote: > > On Sunday September 16, mfedyk@matchmail.com wrote: > > > Hi, > > > > > > I'm trying to

Hi all, and particularly Andrew and Stephen, I recently "upgraded' one of my NFS fileservers from (patched)2.4.18 to 2.4.23-pre7 (in order to resolve a HIMEM related memory pressure problem). Unfortunately I have experienced what appears to be a deadlock. The one I will describe was experienced while running 2.4.23-pre7, though I had a very similar problem in 2.4.22 (but

Hi, I recently upgraded one of my fileservers from 2.4.16 to 2.4.18 plus the ext3-cvs.patch that Andrew Morton pointed me to for addressing and assertion failure. Since then I have been getting lots of errors like: May 21 14:07:03 glass kernel: EXT3-fs error (device md(9,0)): ext3_add_entry: bad entry in directory #2945366: rec_len %% 4 != 0 - offset=0, inode=1886221359, rec_len=24927,

Hi, as I mentioned in earlier mail to ext3-users I have been getting some corruption on an ext3 filesystem that has been serving NFS. I am now confident that I fully understand the problem and have a patch. It only affects data=journal mode and I wonder if it might also be the cause of the corruption noted by a number of people on linux-kernel. First I will explain the problem. Then display

If you export two subvolumes of a btrfs filesystem, they will both be given the same uuid so lookups will be confused. blkid cannot differentiate the two, so we must use the fsid from statfs64 to identify the filesystem. We cannot tell if blkid or statfs is best without knowing internal details of the filesystem in question, so we need to encode specific knowledge of btrfs in mountd. This is

Well.... you might remember that I have had problems will my NFS fileserver that run ext3 with data=journal. The filesystem corruption now seems too be solved with the patch (plus amendment) that I posted, so I am happy about that... but there is more. I have known for a while that ext3 doesn't behave very well when the journal fills up. If it finds that the journal is full, and the

Hi all (and developers in particular) I just got bitten by this Assertion. The one that starts as in the subject, and ends with: "!(((jh2bh(jh))->b_state & (1UL << BH_Lock)) != 0)" Google reminds me that it was mentioned a few times earlier this year, but I couldn't find any statement saying that it has been fixed. I got this in a 2.4.16 kernel, though the

On Monday August 4, akpm@osdl.org wrote: > Daniel Jacobowitz <dan@debian.org> wrote: > > > > I came back this morning and found: > > EXT3-fs error (device md0) in start_transaction: Journal has aborted > > EXT3-fs error (device md0) in start_transaction: Journal has aborted > > EXT3-fs error (device md0) in start_transaction: Journal has aborted >

On 2016-06-01 20:07, Kelly Lesperance wrote: > Software RAID 10. Servers are HP DL380 Gen 8s, with 12x4 TB 7200 RPM drives. > > On 2016-06-01, 3:52 PM, "centos-bounces at centos.org on behalf of m.roth at 5-cent.us" <centos-bounces at centos.org on behalf of m.roth at 5-cent.us> wrote: > > >Kelly Lesperance wrote: > >> I did some additional testing - I

Hello... I have a server with 4 x SCSI drives and I would like to install Centos 4 (or 5) onto a software RAID 10 array. Do you know if this is possible? I noticed that under the Centos 4.92 beta, RAID 5 is an option but for some reason RAID 10 is not listed. There does appear to be a RAID 10 module.... /lib/modules/2.6.9-42.0.8.ELsmp/kernel/drivers/md/raid10.ko More info I found here:

NFS needs a unique identifier for a filesystem to be able to export it. This can be set by the admin (fsid= in /etc/exports) but that is a hassle and it is best to set it automatically. nfs-utils currently uses the UUID returned by libblkid if that works, or the fsid returned by statfs64 if libblkid finds nothings and fsid is non-zero. Otherwise it uses device major/minor. This

Hi all, we observed a strange effect when copying an file within a samba share: Both atime an mtime of the target file are set to the mtime of the original file. The atime of the original file is updated to the current time. 1. Status of the original file: # stat test.txt File: `test.txt' Size: 3 Blocks: 8 IO Block: 4096 regular file Device: 811h/2065d

Hi, I am trying out ext3 with an external journal (on a battery backed RAM card). I use data=journal, and sync nfs writes go nice and fast :-) But.. I had to power cycle it (buggy VM.. grumble :-) and now I cannot get my filesystem back. It is only a test filesystem so I don't need the data. But I want this to work before I put real data on it. If I "fsck /dev/md1", it

Hi, there appears to be a bug w.r.t. chown and quotas in ext3. In particular, if you "chown" a file on a filesystem with userquotas enabled, the quota charge in not transfered. ditto "chgrp" and group quotas. This happens because i_op->setattr has been redefined for files, and ext3_setattr doesn't do the DQUOT_TRANSFER like it should. I have fixed it by adding a

Hi I have just upgraded from R2.6.0 to R2.7.1 (running on Windows) and a part of my code that previously ran ok now gives an error. The following is a simple example to demonstrate my problem. > a <- array(c(1,2,3,4,5,6,rep(NA,6)),dim=c(6,2)) > apply(a,2,sd,na.rm=T) In R2.6.0 this gives (which is what I would like) [1] 1.870829 NA In R2.7.1 it gives the following error

Hi, originally I posted this to linux-raid@vger.kernel.org, but I guess there are chances that someone in here might comment on it as well. TIA. * Neil Brown <neilb@cse.unsw.edu.au> [2003-03-20 10:58]: > On Thursday March 20, lists@schlich.org wrote: > > > > And when I try to mount the array: > > --8<-- > > EXT3-fs error (device md(9,1)):

This was sent to lkml, I think it may be interesting to this list... ----- Forwarded message from "J . A . Magallon" <jamagallon@able.es> ----- Envelope-to: mfedyk@mikef-linux-x86.matchmail.com Delivery-date: Fri, 02 Nov 2001 16:38:49 -0800 From: "J . A . Magallon" <jamagallon@able.es> To: Lista Linux-Kernel <linux-kernel@vger.kernel.org> Subject: ext3 for

I have been playing with external journals some more and thought I should share some experiences. I am running 2.4.16 with the ext3 patches from Andrew Morton and e2fsprogs 1.25 I have an ext3fs filesystem on an 8 drive RAID5 array and place the journal on a partition of the mirrored pair that I boot off (all drives SCSI). I have tried pulling the power cable and seeing what happens. I finally