On Monday January 15, [EMAIL PROTECTED] wrote:
On Mon, 15 Jan 2001, Jure Pecar wrote:
There is something not that usual about my setup: i run raid1 /boot and
raid5 root with one disk disconnected (its simply too loud...), so the
array is in degraded mode all the time. Other
On January 16, [EMAIL PROTECTED] wrote:
Unable to handle kernel NULL pointer dereference at virtual address 0003
c01ccf91
*pde =
Oops: 0002
CPU:0
EIP:0010:[c01ccf91]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010086
eax: ebx: c1490400
There have been assorted reports of filesystem corruption on raid5 in
2.4.0, and I have finally got a patch - see below.
I don't know if it addresses everybody's problems, but it fixed a very
really problem that is very reproducable.
The problem is that parity can be calculated wrongly when
On Monday January 22, [EMAIL PROTECTED] wrote:
In article [EMAIL PROTECTED] you wrote:
There have been assorted reports of filesystem corruption on raid5 in
2.4.0, and I have finally got a patch - see below.
I don't know if it addresses everybody's problems, but it fixed a very
really
On January 22, [EMAIL PROTECTED] wrote:
We have a LAN with about 40 Linux systems on it. We use the Berkeley
"customs" suite to perform parallelized builds of our product. So we
hammer NFS pretty hard; 30-40 machines can be simultaneously reading
and writing a single build tree through
On Wednesday January 24, [EMAIL PROTECTED] wrote:
(Please consider removing FreeBSD-stable from the recipient list when
replying.)
freebsd-stable removed! reiserfs gone. Who goes next:-? Alan?
Summary:
The Linux 2.2.18 NFS v3 server returns bogus and as per RFC-1813 invalid
NFS3ERR_ROFS
On Monday January 29, [EMAIL PROTECTED] wrote:
linux-2.4.1p11-1/drivers/md/md.c
line 3643
-#define MAX_MD_BOOT_DEVS 8
+#define MAX_MD_BOOT_DEVS MAX_MD_DEVS
---
To: Dave Cinege [EMAIL PROTECTED]
On Mon, 29 Jan 2001, Dave
On Thursday January 25, [EMAIL PROTECTED] wrote:
On Wed, 24 Jan 2001, Matthias Andree wrote:
This looks better and it makes FreeBSD able to ls the directory, and on
touch /mnt/try, I get EROFS on the client, so this is okay; however, the
access reply does not include EXECUTE permissions
On Monday May 14, [EMAIL PROTECTED] wrote:
End of discussion.
Linus
...and start of education please...
I want to create a new block device - it is a different interface to
the software-raid code that allows the arrays to be partitioned using
normal partition tables.
So I
On Monday May 14, [EMAIL PROTECTED] wrote:
Neil Brown wrote:
So I need a major number - to give to devfs_register_blkdev at least.
You don't want me to have a hardcoded one (which is fine) so I need a
dynamically allocated one - yes?
This means that we need some analogue to {get,put
On Monday May 14, [EMAIL PROTECTED] wrote:
This means that we need some analogue to {get,put}_unnamed_dev that
manages a range of dynamically allocated majors.
Is there such a beast already, or does someone need to write it?
What range(s) should be used for block devices?
Am I
On Monday May 14, [EMAIL PROTECTED] wrote:
On Tue, 15 May 2001, Neil Brown wrote:
I want to create a new block device - it is a different interface to
the software-raid code that allows the arrays to be partitioned using
normal partition tables.
See the other posts about creating
On Tuesday May 15, [EMAIL PROTECTED] wrote:
On Tue, 15 May 2001, Neil Brown wrote:
Ofcourse setting the queue function that __blk_get_queue call to do
a lookup of the minor and choose an appropriate queue for the real
device wont work as you need to munge bh-b_rdev too.
What I
On Friday September 1, [EMAIL PROTECTED] wrote:
2: incompatible tools: those who follow a dist are already using
incompatible tools anyway, and can either stay with their dist or get
the neccessary tools themselves (nfs-utils is available in RPM and
deb anyway!). those who follow the stock
On Saturday September 2, [EMAIL PROTECTED] wrote:
Linus,
The attached patch is submitted to enable variable sector size block
chaining via ll_rw_block() in the I/O subsystem layer.
Jeff904a905,907
/
// This code is being commented out to allow support for variable chained
//
On Friday September 29, [EMAIL PROTECTED] wrote:
On Fri, 29 Sep 2000, Pavel Machek wrote:
Are you sure there are no deadlock-when-low-on-memory bugs
hiding somewhere? swap over nbd also *seems* to work.
Raid preallocates all the memory that it needs.
When raid1 runs out of pre-allocated
On Friday October 6, [EMAIL PROTECTED] wrote:
Neil Brown wrote:
Suppose, for stripe X the parity device is device 1 and we were
updating the block on device 0 at the time of system failure.
What had happened was that the new parity block was written out, but
the new data block wasn't
On Saturday October 7, [EMAIL PROTECTED] wrote:
Matt Stegman writes:
A few weeks ago Alan Cox mentioned, in reply to someone asking about
building an enourmous RAID array,
"Right now 2.2 doesnt support journalling over software raid so that would
stop you using reiserfs and ext3."
On Saturday February 24, [EMAIL PROTECTED] wrote:
I have my home directory mounted on one computer from another. I
rebooted the server and now the client is saying Stale NFS file handle
anytime something goes to read my home directory. It has been this
way for about a day. Shouldn't any
On Saturday February 24, [EMAIL PROTECTED] wrote:
[problem summary: After restarting knfsd server on 2.4.2, client
reports Stale NFS file handle]
On Sun, Feb 25, 2001 at 04:43:46PM +1100, Neil Brown wrote:
So check that /etc/exports contains the right info.
Check that /var
On Sunday February 25, [EMAIL PROTECTED] wrote:
On Sun, Feb 25, 2001 at 08:25:10PM +1100, Neil Brown wrote:
On Saturday February 24, [EMAIL PROTECTED] wrote:
Verrry odd. I can see why you were suspecting a cache.
I'm probably going to have to palm this off to Trond, the NFS client
On February 28, [EMAIL PROTECTED] wrote:
" " == Neil Brown [EMAIL PROTECTED] writes:
So... you can access things under /home/david, but you cannot
access /home/david itself? So, supposing that "fred" were some
file that you happen to kn
On Friday March 2, [EMAIL PROTECTED] wrote:
1. Problem description
2. Machine details
a) Hardware
b) Software
3. System log during the incident
1. Problem Description:
snip
Mar 2 13:44:38 bertha kernel: Unable to handle kernel NULL pointer
dereference at virtual address
On Wednesday March 7, [EMAIL PROTECTED] wrote:
I run a Dual prozessor SMP system on 2.4.2-ac12 for a while
in degraded mode. Today I put in a new disk to switch to
full raid5 mode. Shortly after the command raidhotadd the
system crashed with the message lost interrupt on cpu1.
Was there an
On Thursday March 8, [EMAIL PROTECTED] wrote:
On Thu, 8 Mar 2001 08:55:28 +1100 (EST), Neil Brown wrote:
On Wednesday March 7, [EMAIL PROTECTED] wrote:
I run a Dual prozessor SMP system on 2.4.2-ac12 for a while
in degraded mode. Today I put in a new disk to switch to
full raid5 mode
Linus,
in 2.4.3-pre3, drivers/net/3c509.c will not compile ifdef CONFIG_ISAPNP.
The following patches fixes the error. I suspect that 3c515.c has
the same problem, but I didn't need to fix that to get my kernel to
build... so I didn't.
NeilBrown
--- ./drivers/net/3c509.c
On Friday March 16, [EMAIL PROTECTED] wrote:
Here are some more results from the MC project. These are 16 errors found
in 2.4.1 related to inconsistent use of locks. As usual, if you can
verify any of these or show that they are false positives, please let us
know by CC'ing [EMAIL
On Monday November 20, [EMAIL PROTECTED] wrote:
Hi all. 2.4.0-test11 is crashing during bootup while
detecting my raid5 array. According to the EIP printed (assuming
I did it right), that's in the function xor_block().
2.4.0-test10 works fine with the same .config. One of
On Monday November 20, [EMAIL PROTECTED] wrote:
Here´s the output of ksymoops:
EIP; c01c8e66 xor_block+46/90 =
In drivers/md/Makefile, swap the order of "raid5.o xor.o" to be "xor.o
raid5.o", recompile, install, reboot.
NeilBrown
-
To unsubscribe from this list: send the line
On Tuesday November 21, [EMAIL PROTECTED] wrote:
On Monday November 20, [EMAIL PROTECTED] wrote:
Hi all. 2.4.0-test11 is crashing during bootup while
detecting my raid5 array. According to the EIP printed (assuming
I did it right), that's in the function xor_block().
On Tuesday November 21, [EMAIL PROTECTED] wrote:
Hi,
I want to know , how to Benchmark the performance of
RAID.Is there any tool for benchmarking?
It all depends on what you want to measure.
If you want to measure "how well will this work for me", then you need
a tool that generates a
On Thursday November 23, [EMAIL PROTECTED] wrote:
I just got these while doing many compiles on my box
Nov 23 00:40:06 viper kernel: EXT2-fs warning (device ide0(3,3)):
ext2_unlink: Deleting nonexistent file (622295), 0
Nov 23 00:40:06 viper kernel: = 1
Nov 23 00:40:06 viper kernel:
On Thursday November 23, [EMAIL PROTECTED] wrote:
Guys, could you try to reproduce it with the following:
Well, I tried but it didn't go real well.
I build a 2 drive raid5 array (the script goes on to 3,4,5,6,7 drive
arrays), ran mkfs, mounted, ran "hdparm -t" on /dev/md0, ran bonnie.
So
On Thursday November 23, [EMAIL PROTECTED] wrote:
On Thursday November 23, [EMAIL PROTECTED] wrote:
Guys, could you try to reproduce it with the following:
Well, I tried but it didn't go real well.
.
It looks like extending a file is not allowed any more.
This is with
On Tuesday November 21, [EMAIL PROTECTED] wrote:
This may be 2.2.18 material after all I wrote last night:
Making nfsd's d_splice() compensate for d_move's limitations is not
only a kludge, but also it harder to keep nfsd correct.
someday, nfsd may not be the only creator of this kind
On Thursday November 23, [EMAIL PROTECTED] wrote:
On Thu, 23 Nov 2000, Alexander Viro wrote:
On Thu, 23 Nov 2000, Neil Brown wrote:
which enabled ext2_notify_change, however ext2_notify_change has a
bug.
It sets attributes from iattr-ia_attr_flags even
if ATTR_ATTR_FLAG
On Friday November 24, [EMAIL PROTECTED] wrote:
... RedHat's GCC snapshot "2.96" handles this case just fine.
Now, if you can isolate the relevant part of the diff between
2.95.2 and RH 2.96...
Maybe I have to be more precise in the statement "gcc 2.95.2 is buggy".
I just installed
On Friday November 24, [EMAIL PROTECTED] wrote:
On Fri, 24 Nov 2000, Neil Brown wrote:
I ran my test script, which builds a variety of raid5 arrays with
varying numbers of drives and chunk sizes, and runs mkfs/bonnie/dbench
on each array, and it got through about 8 file systems
On Monday November 27, [EMAIL PROTECTED] wrote:
Oh, well. Some people saw the (unannounced, and not for public
consumption) pre1, so here's pre2. pre1 was just meant to be an interim
patch to sync up with the ISDN patches.
Due to the birth of my third daughter last week (yes, I got
Linus,
I thought I would document what I had learnt about Makefiles in
making the initialisation of drivers/md work better.
This patch (minus a few typos that I have since found and corrected)
was blessed by Michael Chastain on linux-kbuild.
Ofcourse, running "make vmlinux" doesn't
On Sunday November 26, [EMAIL PROTECTED] wrote:
Neil Brown wrote:
The following patch changes the link order in the Makefile so that xor
is initiailised before md tries to autostart anything.
It also takes the theme a bit further and uses module_init/module_exit
to init and shutdown
On Friday December 1, [EMAIL PROTECTED] wrote:
Please CC to me because I'm not a LKML subscriber.
Hi,
I found a real showstopper problem in the SoftwareRAID autodetect
code; 2.4.0-test10 and 2.4.0-test11 are affected (I didn't test
previous versions).
Fixed in 2.4.0-test12pre3.
If you
Linus, Ingo:
the attached patch, modifies a warning message in md.c which seems to
often cause confusion - the following email includes one example
there-of (there have been others over the months).
Hopefully the new text is clearer.
(patch against 2.4.0-test11-pre7)
NeilBrown
On
Alan,
raid5 rebuild has been fatally flawed ever since it got into 2.4, and
my recent testing has been looking at speed more than correctness, so
I didn't notice until now.
raid5_sync_request is handed a block number in 1K units and needs to
convert to 512byte sector units.
I could have
On Friday December 1, [EMAIL PROTECTED] wrote:
On Fri, Dec 01, 2000 at 01:11:45PM +1100, Neil Brown wrote:
On Thursday November 30, [EMAIL PROTECTED] wrote:
Hello people,
I have some trouble with the raid-stuff.
...
Is it just "very slow", but it eventually finishes, i
On Wednesday November 15, [EMAIL PROTECTED] wrote:
[Ian Grant [EMAIL PROTECTED]]
Of course we need an initrd with the raid modules on it before we can
boot from a RAID root partition.
raidtools can't run from an initrd?
Peter
There is a realy issue here.
raidstart currently does not
On Thursday November 30, [EMAIL PROTECTED] wrote:
Hello people,
I have some trouble with the raid-stuff.
My machine is a Pentium-III, 256 MB ram and 7 scsi-disks (IBM DNES-318350W
17B). I'm using raid5 for 6 of these disks (chunk-size 8).
Machine boots, I do mkraid /dev/md0 and then mke2fs
Linus,
below is a patch for 2.4.0-test that adds documentation for
ll_rw_block and generic_make_request. It also corrects a type error
in a printk call.
I would really like to change a couple of names in the file:
"generic_make_request" would sound much better as "raw_rw_block".
that
On Monday December 4, [EMAIL PROTECTED] wrote:
On 01-Dec-00, Neil Brown wrote:
On Friday December 1, [EMAIL PROTECTED] wrote:
I found a real showstopper problem in the SoftwareRAID autodetect
code; 2.4.0-test10 and 2.4.0-test11 are affected (I didn't test
previous versions).
[detailed
On Wednesday December 6, [EMAIL PROTECTED] wrote:
Peter Samuelson wrote:
[Roberto Ragusa]
BTW, here is a little patch regarding a silly problem I found
about RAID partitions naming (/proc/partitions).
No more "md8" "md9" "md:" "md;" ... but "md8" "md9" "md10" "md11" ...
Well,
On Wednesday December 6, [EMAIL PROTECTED] wrote:
Neil Brown wrote:
here we have lost the "part" automatic variable in disk_name but
I don't think so. Look again.
Gulp... :-(
Yes, your patch is indeed fine. I heartily recommend it (for whatever
that is wor
On Tuesday December 12, [EMAIL PROTECTED] wrote:
On Tue, Dec 12, 2000 at 11:06:07AM -0800, Linus Torvalds wrote:
To get better debug output, could you please do something for me?
In fs/buffer.c, get rid of "end_buffer_io_bad" completely, and replace all
users of it with NULL.
On Tuesday December 12, [EMAIL PROTECTED] wrote:
On Wed, 13 Dec 2000, Neil Brown wrote:
Could you add this test to the top of md_make_request as well, because
requests to raid5 don't go through generic_make_request.
Sure they do. Everything that calls ll_rw_block() or submit_bh
On Tuesday December 12, [EMAIL PROTECTED] wrote:
On Wed, 13 Dec 2000, Neil Brown wrote:
Yes... you are right. Alright, I can't escape it any other way so I
guess I must admit that it is a raid5 bug.
But how can raid5 be calling b_end_io on a buffer_head that was never
passed
On Thursday December 14, [EMAIL PROTECTED] wrote:
Dear kernel maintainers,
I will report my problem around 2.4.0-test kernel.
Thanks in advance.
The simplest fix for this is the patch below. Exactly what will get
into test13 has not yet been decided.
NeilBrown
--- drivers/md/raid5.c
On Monday December 18, [EMAIL PROTECTED] wrote:
" " == M H VanLeeuwen [EMAIL PROTECTED] writes:
Trond, Neil I don't know if this is a loopback bug or an NFS
bug but since nfs_fs.h was implicated so I thought one of you
may be interested.
Could you let me know if
On Tuesday December 19, [EMAIL PROTECTED] wrote:
I've been getting tonnes of these since I installed 2.2.18. Is this a
problem? Should I even worry about this? If I don't need to worry about
it, is there a way to stop displaying this message?
fh_lock_parent: mqueue/xfBAA14279 parent
On Thursday December 21, [EMAIL PROTECTED] wrote:
Hi. I am having strange nfs problems in both my 2.x and 2.4.0-test12
kernels.
What is happening is that when the machine boots up and exports the
directories for nfs, it complains that
ccs2:/ invalid argument .
The exports entry is
On Thursday December 21, [EMAIL PROTECTED] wrote:
On Fri, 22 Dec 2000, Neil Brown wrote:
On Thursday December 21, [EMAIL PROTECTED] wrote:
Hi. I am having strange nfs problems in both my 2.x and 2.4.0-test12
kernels.
What is happening is that when the machine boots up
On Friday December 29, [EMAIL PROTECTED] wrote:
Hi,
On the server:
bash$ ls -l
total 21
drwxrwxrwx 11 root root 2048 Jul 23 02:32 arm
lrwxrwxrwx 1 root root 14 Aug 22 1999 dg -
/home/gilbertd
drwxr-xr-x 6 root root 1024 Mar 21 1999 ftp
On Friday December 29, [EMAIL PROTECTED] wrote:
On Sat, 30 Dec 2000, Neil Brown wrote:
So where did the gilbertd directory go ?
It suffered the curse of the 8-character file name
Can you get a tcpdump (-s 1024) of the network traffic while this is
happening?
Yep; to avoid
[ extra detail included because I have added linux-alpha and lins to
the cc list]
It appears that memmove is broken on the alpha architecture.
memmove is used by net/sunrpc/xdr.c:xdr_decode_string
to move a string 4 bytes down in memory.
memmove(X-4, X, 8) should change
X: 00 00 00 08
On Saturday December 30, [EMAIL PROTECTED] wrote:
On Friday December 29, [EMAIL PROTECTED] wrote:
Hi -- could you please CC me if you reply to this mail.
A: /exports/A - Redhat 7.0
B1/B2: mount /exports/A on /export/A from A - Redhat 6.2
On Tuesday January 2, [EMAIL PROTECTED] wrote:
Perhaps a deadlock with a normal (not irq) spinlock.
Could you enable SysRQ and press Alt+SysRq+P ("showPc")
Then write down the EIP values (including the [ ] brackets) and
translate them with ksymoops.
Ksymoops repeats only the EIP
Linus/Alan,
please accept the following patch for knfsd in 2.4.0-prerelease.
What it does is extend the protection offered by s_nfsd_free_path_sem
to cover the first call to nfsd_iget.
I had previously avoided this as I didn't think it was necessary and
it ment that the semaphore wasn't
On Wednesday January 3, [EMAIL PROTECTED] wrote:
On Tue, 02 Jan 2001 18:19:41 +0100, Otto Meier wrote:
Dual Celeron (SMP,raid5)
As stated in my first mail I run actually my raid5 devices in degrated mode
and as I remenber there has been some raid5 stuff changed between
test13p3 and
On Sunday January 7, [EMAIL PROTECTED] wrote:
Hi,
on my machine (x86) I've debian2.2r2 with kernel 2.2.16 + raidtools 0.9
running. No problems. Yesterday I installed kern 2.4.0 with the same
configuration like 2.2.16. I added following to the boot params:
root=/dev/md0
On Monday January 1, [EMAIL PROTECTED] wrote:
On Thu, Dec 21, 2000 at 12:05:41PM +1100, Neil Brown wrote:
So, I have started putting some patches together and they can be
found at
http://www.cse.unsw.edu.au/~neilb/patches/knfsd-2.2/
I included the interesting ones in my tree
On Friday October 27, [EMAIL PROTECTED] wrote:
This was first reported in 2.2.12, according to Deja. Solaris clients,
on rare occaisons, will send some command to a linux server which
causes a null resp-fh.fh_dentry to be passed to routines in
/usr/src/linux/fs/nfsd/nfsxdr.c. This causes an
Linus,
There is a problem with drivers/block/rd.c which can lead to a
deadlock an SMP hardware.
The scenario goes:
Processor A Processor B
enter _make_request in getblk (or elsewhere)
(or generic_unplug_device)
On Friday November 10, [EMAIL PROTECTED] wrote:
Any suggestions?
Yes, send the details to the author of the code, as detemined from
the comment above it:
Richard Henderson ([EMAIL PROTECTED])
After having written:
I've tried this on -test9, test10, and test11-pre2, all with similar
On Friday November 10, [EMAIL PROTECTED] wrote:
Hi,
I made some optimizations on racache in nfsd in test10. The idea is to
replace with existing fixed length table for readahead cache in NFSD with a
hash table.
The old racache is essentially ineffective in dealing with large # of
files,
On Sunday November 12, [EMAIL PROTECTED] wrote:
Rasmus Andersen wrote:
I tried to include linux/types.h in md.c and had to include
linux/blkdev.h also. Otherwise I got the following:
Here is the solution I prefer... md builds fine with this, core kernel builds fine
with this, and
I'm
While reading a recent discussion of highmem support in ramfs, I was
reminded that my recent patch to rd.c removed highmem support (as that
support came through the create_bounce call in __make_request, and
with my change, rd requests no longer go though __make_request).
The following patch
(please remove linux-kernel from future followups)
On Sunday November 12, [EMAIL PROTECTED] wrote:
Hello,
(I hope this is not the wrong mailing list to ask this question..)
Not "wrong" exactly, but not "best" either.
Look in the MAINTAINERS file of a recent kernel source tree, look for
On Sunday November 12, [EMAIL PROTECTED] wrote:
Hi,
This is the recoded racache that uses list_head for several lists, e.g.,
lru and free lists. I have tested it under SPEC SFS runs, and several other
NFS loads myself.
Ok, I have taken a closer look at this code:
1/ Why did you change
On Wednesday November 15, [EMAIL PROTECTED] wrote:
[1.] knfsd causes file system corruption when files are locked.
[2.] Lock down a file using the NLM_SHARE sharing mechanism. Remove
the file. Unlock the file using NLM_UNSHARE. The filesystem does not
recover the file space. I am running
On Thursday November 16, [EMAIL PROTECTED] wrote:
FYI:
gcc -D__KERNEL__ -I/usr/src/linux-2.4.0-test11/include -Wall -Wstrict-prototypes -O2
-fomit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2
-march=i686-c -o dev.o dev.c
dev.c: In function `run_sbin_hotplug':
On Tuesday May 8, [EMAIL PROTECTED] wrote:
Hi,
I'm using kernel 2.4.4 cvs from SGI, with xfs. I'm getting this Oops:
kernel: Unable to handle kernel NULL pointer dereference at virtual address 0010
kernel: printing eip:
kernel: c017bfd8
kernel: *pde =
kernel: Oops:
On Saturday June 9, [EMAIL PROTECTED] wrote:
Hi All,
I get this panic running RedHat 2.4.3-6:
Unable to handle kernel NULL pointer dereference at virtual address 0004
c014b13d
The problem is pretty specific to 2.4.3-6 because it has code in list_del() to
null out the prev
On Tuesday June 12, [EMAIL PROTECTED] wrote:
Hi. I seem to remember that at one time in the 2.2 series I was able
to to export fat32 file systems using nfs, but now it doesn't work
anymore.
No, it doesn't.
It did in early 2.2 due to some fairly ugly hacks which just had to
go. They worked
On Tuesday June 12, [EMAIL PROTECTED] wrote:
On Wed, 13 Jun 2001, Neil Brown wrote:
Call fat_iget(i_location).
If this finds something, check i_logstart.
If it matches, assume SUCCESS.
Then comes the tricky bit: read the directory entry
indicated
On Wednesday June 13, [EMAIL PROTECTED] wrote:
I might just do that first step (find_ino) and offer it as as an
experimental patch to the growing number of people who have asked for
nfs exporting of FAT filesystems, and see how reliable it is in
practice.
Following is a patch against
On Tuesday June 19, [EMAIL PROTECTED] wrote:
On Mon, Jun 18, 2001 at 11:57:16PM -0400, Shawn Starr wrote:
read_super_block: can't find a reiserfs filesystem on dev 03:42
read_old_super_block: try to find super block in old location
read_old_super_block: can't find a reiserfs filesystem
On Sunday June 24, [EMAIL PROTECTED] wrote:
Hi,
Since I switched to the kernel nfsd I have troubles exporting my
filesystems. I think in kernel 2.2.x there was no problem, neither was
it with the userspace nfsd. Currently I run kernel 2.4.5pre1 on the
server.
Sounds like you might have an
On Thursday July 5, [EMAIL PROTECTED] wrote:
Hello linux-kernel,
Does anyone have information on this subject ? I have the constant
failures with system swapping on RAID1, I just wanted to be shure
this may be the problem or not. It works without any problems with
2.2 kernel.
On Thursday February 1, [EMAIL PROTECTED] wrote:
hi,
i using kernel 2.4.1. mkraid version 0.90.0
i build /dev/md0 raid-0 with hda5 and sda1. then i build /dev/md1 raid-1
with /dev/md0 and sdb1.
it works fine.
BUT the resync takes a long time. i have a performance from 253K/sec.
whats
On Monday February 5, [EMAIL PROTECTED] wrote:
Seems recently, on both redhat 6.1 and 7.0 using kernel 2.4.1-ac3, I
ran into this problem:
Stopping NFS says the following in the kernel logs:
nfsd: terminating on signal 9
nfsd: terminating on signal 9
nfsd: terminating on signal 9
nfsd:
On Monday February 5, [EMAIL PROTECTED] wrote:
On Tue, 6 Feb 2001, Neil Brown wrote:
How repeatable is this? Is the server SMP?
I've tested this on two UP Athlons and 2 SMP Pentium 3's and the same problem
occurred. I have not tested it more than once on the same system (I left the
NFS
On Wednesday February 7, [EMAIL PROTECTED] wrote:
Hi,
I have a strange problem on one of our server.
I have 2.4.1 patched with ACLs 0.7.5 (from acl.bestbits.at) and some RAID +
LVM volumes.
At regular interval, NFS stops working (nfsd stops) and a stop/start of the
NFS service doesn't
On Wednesday February 7, [EMAIL PROTECTED] wrote:
On Wed, 7 Feb 2001, Christoph Hellwig wrote:
On Tue, Feb 06, 2001 at 12:59:02PM -0800, Linus Torvalds wrote:
Actually, they really aren't.
They kind of _used_ to be, but more and more they've moved away from that
On Wednesday February 14, [EMAIL PROTECTED] wrote:
Hi all,
I have a machine with kernel 2.4.1 + acls patch. It exports some volume via
NFS (installed with RedHat 7.0 + custom 2.4.1 kernel). The underlying
filesystem is ext2. I tried with NFS v2 and v3 and without ACLs in the
kernel.
On Thursday February 15, [EMAIL PROTECTED] wrote:
Here I am again! NFSD died at 11h23, ~12 hours after the last reboot, a
record :-)
I'm guessing you don't have many symlinks on the exported
filesystem
I'll try to best answer your questions.
This trace seems to make sense, except
On Sunday February 18, [EMAIL PROTECTED] wrote:
Hi,
I migrated some exported disks over to reiserfs and had no luck when I
mounted the disk via NFS on another machine. I've noticed many messages
about reiser and NFS in the archives, but my understanding was that
it had been cleared up.
On Sunday February 18, [EMAIL PROTECTED] wrote:
On Sun, Feb 18, 2001 at 12:57:14AM -0800, Dan Hollis wrote:
The XOR patent and the fraudulent enforcement of it is the purest
embodiment of everything that is wrong with the patent system and IP law.
On Sun, 18 Feb 2001 [EMAIL
On Sunday February 18, [EMAIL PROTECTED] wrote:
OK, I grabbed these patches and applied them against 2.4.2-pre4 and
recompiled, rebooted. I am now able to use reiserfs with NFS,
basic operations appear to work as expected but I haven't done large amounts
of file IO or lots of concurrent
On Monday February 19, [EMAIL PROTECTED] wrote:
I hope to put out a patch set for testing in a day or so and possibly
suggest it to Alan for his -ac series. I don't see it going into
2.4.2, but 2.4.3 might be possible if Linus agrees.
Im not interested in a patch that requires NFS is
On Monday February 19, [EMAIL PROTECTED] wrote:
On Tuesday, February 20, 2001 11:40:24 AM +1100 Neil Brown
[EMAIL PROTECTED] wrote:
When reiserfs came along, it abused this, and re-interpreted the
opaque datum to contain information for recalling (locating) an
inode
On Tuesday February 20, [EMAIL PROTECTED] wrote:
This may seem like a lot, but several of these are already
requirements which most filesystems don't meet, and other are there
to tidy-up interfaces and make locking more straight forward.
As a 2.5 thing it sounds like a very sensible
On Tuesday February 20, [EMAIL PROTECTED] wrote:
Hi,
On Tue, 20 Feb 2001, Neil Brown wrote:
2/ lookup("..").
A small question:
Why exactly is this needed?
bye, Roman
Having read the subsequent posts, I now see what you are thinking and
know how to answer this.
The prob
1 - 100 of 944 matches
Mail list logo
