search for: neilbrown

On 06/27/2011 07:46 AM, NeilBrown wrote: > On Thu, 23 Jun 2011 12:53:37 +0200 Nico Schottelius > <nico-lkml-20110623@schottelius.org> wrote: > >> Good morning devs, >> >> I''m wondering whether the raid- and volume-management-builtin of btrfs is >> actually a sane idea or not. >&gt...

...ecific knowledge of btrfs in mountd. This is unfortunate. To ensure smooth handling of this and possible future changes in uuid generation, we add infrastructure for multiple different uuids to be recognised on old filehandles, but only the preferred on is used on new filehandles. Signed-off-by: NeilBrown <neilb-l3A5Bk7waGM@public.gmane.org> -- This is a substantially revised version of a patch I posted a while ago. I tried to find a way to do it would hard coding knowledge of btrfs in nfs-utils, but it isn''t possible. For some filesystems, f_fsid is best, for some it is worst. No...

...hesising a UUID for a btrfs filesystem. The simplest would be to explicitly ignore btrfs results from libblkid as the following patch does. However this is rather hackish, and wastes half of the bits in the uuid. Can anyone suggest a better way to get a good uuid for a btrfs filesystem? Thanks, NeilBrown diff --git a/utils/mountd/cache.c b/utils/mountd/cache.c index caef5b2..ffc5ac7 100644 --- a/utils/mountd/cache.c +++ b/utils/mountd/cache.c @@ -176,7 +176,8 @@ static const char *get_uuid_blkdev(char *path) blkid_tag_iterate iter; blkid_dev dev; const char *type; - const char *val = NULL; +...

....4-0.9.13, 21 Oct 2001, and e2fsprocs 1.22. I appreciate that there is a 0.9.14 out but the changelog doesn't mention anything about external journals. I created the filesystem and journal as per the instructions on andrewm's ext3 web page. Any patches or suggestions most welcome. NeilBrown

I'm running Linux travis 2.6.15-1-686 #2 Mon Mar 6 15:27:08 UTC 2006 i686 GNU/Linux on a laptop with ext3 on / Some time ago things started getting weird in the following way: I do a fairly normal hack, ^Z, make, test loop when developing and it seems that vim is calling fsync or sync and that is then flushing everything to disk. My tests create maybe 10 dozen files in ~30MB and for some

...me. raid5 tries to apply them in the same order that they were received, but I don't feel confident that means that the *right* thing is happening. These were happening with 2.4.16, but the incidence seems to have increased with 2.4.18 (though that isn't a very strong observation). NeilBrown

...would be keen to here how this patch affects things. The corruption that I see that I blame on this problem is directories begin overwritten with what looks like file contents and in one case (which required 90 minutes downtime for a fsck) some indirect blocks being over-written by file contents. NeilBrown --- ./fs/jbd/commit.c 2002/05/28 04:15:18 1.1 +++ ./fs/jbd/commit.c 2002/05/28 22:44:48 @@ -663,12 +663,13 @@ * there's no point in keeping a checkpoint record for * it. */ bh = jh2bh(jh); - if (buffer_jdirty(bh)) { + if (buffer_jdirty(bh) && !__buffer_state(bh, Freed)) {...

...work, but is hardly elegant. I'm not in a position at the moment to spend time testing whether the inefficacy of bdflush is ext3 specific or applies to ext2 as well. I may try that next week (we have a long weekend coming up). If it applies to ext2, it could be a showstopped for 2.4.19.... NeilBrown

...) to modify the commit process to flush out 'ordered' data without locking the journal? As you might guess, we have a situation where writing large files on a large-memory machine is causing occasional bad fs delays and I'm trying to understand what is going on. Thanks for any input, NeilBrown

I am new to ext3 + external journal. Is there any howto I can look at? this is what I understand 1. mke2fs -O journal_dev /dev/md5 2. mke2fs -J device=/dev/md5 /dev/md0 3. mount /dev/md0 / -t ext3 ( hmm.. what do I need to put on fstab?? ) /dev/md5 is a two drive RAID 1 partition /dev/md0 is a 4 drive RAID 5 partition. questions: 1. I am running RedHat 9.0. what extra software I need to

Sorry this is off-topic, but I'm scrambling to get this system in, google didn't help, and I'm sure someone on this list knows the answer cold. I'm trying to nfs-export a tmpfs disk. I saw a hint from a response about ram disks... which leads to my guess that tmpfs simply doesn't implement some method that nfsd needs. I can probably survive without tmpfs, but I'd like to

...gid != inode->i_gid)) error = DQUOT_TRANSFER(inode, attr) ? -EDQUOT : 0; if (error) return error; into ext3_setattr just after: error = inode_change_ok(inode, attr); if (error) return error; though possibly it should go just before the: rc = inode_setattr(inode, attr); instead. NeilBrown

I'm putting the final touches on kinit, which is the user-space replacement (based on klibc) for the whole in-kernel root-mount complex. Pretty much the one thing remaining -- other than lots of testing -- is to handle automatically mounted md devices. In order to do that, without adding userspace versions of all the paritition code (which may be a future change, but a pretty big one)

...get written to disc at much the same time (hence the "multiple 1 requests"), but the old buffer hits the disc second and so corrupts the filesystem. The bug I found was specific to data=journal mode, and this certainly has more options for buffer aliasing. Were you using data=journal? NeilBrown

I've read through the archives and it looks like people are using ext3 with software RAID with at least some success. I just want to confirm that it works properly. If I convert my md RAID 0 to ext3, should I expect A) A fast journalled filesystem, or B) Wailing and gnashing of teeth My RAID currently does not use persistant superblocks, because I created it many moons ago under the old

An update of the ext3 journalling filesystem for 2.4 kernels is available at http://www.uow.edu.au/~andrewm/linux/ext3/ Patches are against 2.4.6-ac1 and 2.4.6. Changes since 0.0.8 include: - Multiplied the version numbering by ten to cater for bugfix releases against the 0.9.0 stream. - The main thrust has been the removal of a number of changes in the core kernel which were required

...ve. It could be simply that a crash at the wrong time could leave the filesystem corrupted. But I heard of one person who claimed to get filesystem corruption after using reiserfs over RAID1 in 2.2, so maybe it's worse than that. If you really need to know, I suggest you ask on ext3-users. NeilBrown ----- End forwarded message ----- Hello, As requested, I have forwarded this thread to ext3-users, and I'm asking the question again here. Were there any specific steps needed to reproduce the error, and with some testing help from me, would anyone be willing to try to fix this bug? Thanks,...

...ter the rebuild finished, I got an ext3 error (see log below) and the journal aborted, and then nfsd Oopsed inside ext3. I rebooted and fscked the filesystem and it found nothing interesting - see output below. So I suspect ext3 has a problem somewhere. I'll see if I can break it again :-) NeilBrown Aug 6 15:22:05 adams kernel: EXT3-fs error (device md1): ext3_add_entry: bad entry in directory #41 009295: rec_len is smaller than minimal - offset=0, inode=3265411686, rec_len=0, name_len=0 Aug 6 15:22:05 adams kernel: Aborting journal on device sda4. Aug 6 15:22:05 adams kernel: ext3_abort...

...lay to a resync. The previous long sleep (1s) has proven unnecessary, even very short delay brings performance right. The change also applied to raid1. The problem has not been observed on raid1, however it shares barriers code with raid10 so it might be an issue for some setup too. Suggested-by: NeilBrown <neilb at suse.com> Link: http://lkml.kernel.org/r/20160609134555.GA9104 at proton.igk.intel.com Signed-off-by: Tomasz Majchrzak <tomasz.majchrzak at intel.com> --- drivers/md/raid1.c | 7 +++++++ drivers/md/raid10.c | 7 +++++++ 2 files changed, 14 insertions(+) diff --git a/drivers...

Hi all, We are observing a consistent interval of about 4 minutes at which there are large sustained writes to disk that causes mysqld to block and not respond for the entire period. We are using data=journal with a 128M journal and the filesystem is 150GB in size. We get about 300kb/sec in writes and that will jump to about 2000kb/sec during the periods of large sustained writes. Those