Marcelo Tosatti wrote:
> On Wed, 27 Jun 2001, Xuan Baldauf wrote:
>
> > Hello,
> >
> > I'm not sure wether this is a reiserfs bug or a kernel bug,
> > so I'm posting to both lists...
> >
> > My linux box suddenly was not availbale using ssh|telnet,
Marcelo Tosatti wrote:
On Wed, 27 Jun 2001, Xuan Baldauf wrote:
Hello,
I'm not sure wether this is a reiserfs bug or a kernel bug,
so I'm posting to both lists...
My linux box suddenly was not availbale using ssh|telnet,
but it responded to pings. On console login, I could type
Urban Widmark wrote:
> On Mon, 21 May 2001, Xuan Baldauf wrote:
>
> > That is annoying, because it heavily slows down bulk transfers of small
> > writes, like automatically unzipping a new mozilla build from the linux box to
> > the windows box. Every write of say
Urban Widmark wrote:
On Mon, 21 May 2001, Xuan Baldauf wrote:
That is annoying, because it heavily slows down bulk transfers of small
writes, like automatically unzipping a new mozilla build from the linux box to
the windows box. Every write of say 100 bytes is implemented as
send
Urban Widmark wrote:
> On 7 May 2001, Linus Torvalds wrote:
>
> > It has code to do that in smb_revalidate_inode(), but it may be that
> > something else refreshes the inode size _without_ doing the proper
> > invalidation checks. Or maybe Urban broke that logic by mistake while
> > fixing the
Urban Widmark wrote:
On 7 May 2001, Linus Torvalds wrote:
It has code to do that in smb_revalidate_inode(), but it may be that
something else refreshes the inode size _without_ doing the proper
invalidation checks. Or maybe Urban broke that logic by mistake while
fixing the other one
hares.
>
> * win9x will sometimes not give back the right filesize, this can cause
> problems when cp'ing a file over an existing one. When truncating the
> file to 0 bytes the server keeps reporting the old size and much
> confusion arises.
> (reported by Xuan Balda
will sometimes not give back the right filesize, this can cause
problems when cp'ing a file over an existing one. When truncating the
file to 0 bytes the server keeps reporting the old size and much
confusion arises.
(reported by Xuan Baldauf, could you verify that this fixes it? If it
does
Urban Widmark wrote:
> On Sun, 1 Apr 2001, Xuan Baldauf wrote:
>
> > there is something wrong with smbfs caching which makes my
> > applications fail. The behaviour happens with
> > linux-2.4.3-pre4 and linux-2.4.3-final.
> >
> > Consider f
Alan Cox wrote:
> > This is a reiserfs security issue, but only of theoretical nature (Even i=
> > f
> > triggered, it won't harm you). But the reason for this bug is in NFS (v2,=
>
> If the blocks contained my old /etc/shadow I'd be a bit upset.
The only bad consequence possible is that you
Alan Cox wrote:
This is a reiserfs security issue, but only of theoretical nature (Even i=
f
triggered, it won't harm you). But the reason for this bug is in NFS (v2,=
If the blocks contained my old /etc/shadow I'd be a bit upset.
The only bad consequence possible is that you possibly
Urban Widmark wrote:
On Sun, 1 Apr 2001, Xuan Baldauf wrote:
there is something wrong with smbfs caching which makes my
applications fail. The behaviour happens with
linux-2.4.3-pre4 and linux-2.4.3-final.
Consider following shell script: (where /mnt/n is a
smbmounted smb share
Hello,
there is something wrong with smbfs caching which makes my
applications fail. The behaviour happens with
linux-2.4.3-pre4 and linux-2.4.3-final.
Consider following shell script: (where /mnt/n is a
smbmounted smb share from a Win98SE box)
router|/mnt/n/temp/smbfs> I=0; while test $I -lt
Hello,
there is something wrong with smbfs caching which makes my
applications fail. The behaviour happens with
linux-2.4.3-pre4 and linux-2.4.3-final.
Consider following shell script: (where /mnt/n is a
smbmounted smb share from a Win98SE box)
router|/mnt/n/temp/smbfs I=0; while test $I -lt
Hello,
about one or two months ago, I had the problem that
/proc/sys/net/ipv4/ip_dynaddr did not work. I analyzed the
problem and somehow came to a solution which I have
forgotten. But a patch which solved the problem against
2.4.1 which also works for 2.4.2-pre4 remained. Here it is.
Xuân.
Chris Mason wrote:
> Hello everyone,
>
> I think Alexander Zarochentcev and I have finally figured out
> cause for null bytes in small reiserfs files.
Alexander, you are the masters! :-) (Yet the others from the reiserfs
team, you are the masters too ;-))
Can you post a message when a kernel
Chris Mason wrote:
Hello everyone,
I think Alexander Zarochentcev and I have finally figured out
cause for null bytes in small reiserfs files.
AlexanderChris, you are the masters! :-) (Yet the others from the reiserfs
team, you are the masters too ;-))
Can you post a message when a
Chris Mason wrote:
> On Thursday, February 08, 2001 10:47:29 AM +1300 Chris Wedgwood
> <[EMAIL PROTECTED]> wrote:
>
> > these appear on your system every couple of days right? if so... are
> > you able to run with the fs mount notails for a couple of days and
> > see if you still experience
Hi Chris,
this is the output of my zero block detection utility. Note that in all the
files mentioned, zero bytes never can exist there, so every zero byte is a bug.
The output format is:
${filename} ${decompressed?"d":"n"} ${startIndex} ${endIndex} ${length}
The data (sorted):
Chris Mason wrote:
> On Wednesday, February 07, 2001 06:30:01 PM +0100 Xuan Baldauf
> <[EMAIL PROTECTED]> wrote:
> > In my case, it's a SIS5513 board.
> >
> > I have to note that I now have one case which is between offset 9260 and
> > 11016. So prob
Chris Mason wrote:
On Wednesday, February 07, 2001 06:30:01 PM +0100 Xuan Baldauf
[EMAIL PROTECTED] wrote:
In my case, it's a SIS5513 board.
I have to note that I now have one case which is between offset 9260 and
11016. So probably the tails unpacking theory does not work out
Hi Chris,
this is the output of my zero block detection utility. Note that in all the
files mentioned, zero bytes never can exist there, so every zero byte is a bug.
The output format is:
${filename} ${decompressed?"d":"n"} ${startIndex} ${endIndex} ${length}
The data (sorted):
Chris Mason wrote:
On Thursday, February 08, 2001 10:47:29 AM +1300 Chris Wedgwood
[EMAIL PROTECTED] wrote:
these appear on your system every couple of days right? if so... are
you able to run with the fs mount notails for a couple of days and
see if you still experience these?
my
"Richard B. Johnson" wrote:
> On Wed, 31 Jan 2001, Keith Owens wrote:
>
> > On Tue, 30 Jan 2001 16:45:16 -0500 (EST),
> > "Richard B. Johnson" <[EMAIL PROTECTED]> wrote:
> > >The subject says it all. `make dep` is now broken.
> > >make[4]: Entering directory `/usr/src/linux-2.4.1/drivers/acpi'
"Richard B. Johnson" wrote:
On Wed, 31 Jan 2001, Keith Owens wrote:
On Tue, 30 Jan 2001 16:45:16 -0500 (EST),
"Richard B. Johnson" [EMAIL PROTECTED] wrote:
The subject says it all. `make dep` is now broken.
make[4]: Entering directory `/usr/src/linux-2.4.1/drivers/acpi'
Peter Horton wrote:
> I'm experiencing repeatable corruption whilst writing large volumes of
> data to disk. Kernel version is 2.4.1-pre8, on an 850MHz AMD Athlon on an
> ASUS A7V (VIA KT133 chipset) motherboard 128M RAM (tested with 'memtest86'
> for 10 hours).
>
> First, I realised that the
Peter Horton wrote:
I'm experiencing repeatable corruption whilst writing large volumes of
data to disk. Kernel version is 2.4.1-pre8, on an 850MHz AMD Athlon on an
ASUS A7V (VIA KT133 chipset) motherboard 128M RAM (tested with 'memtest86'
for 10 hours).
First, I realised that the fsck
und is that I'm unable to log in
to the server when the load is at 200. Apache is already at nice 5 while sshd is
at nice 0.
Xuân.
>
>
> Any other ideas or will I get hacking..
>
> Padraig.
>
> Xuan Baldauf wrote:
>
> > Hello, (maybe a FAQ, but could not find this que
Hello, (maybe a FAQ, but could not find this question)
is it possible with linux2.4 to limit the relative CPU time
per process or per UID? I saw something like this about 5
years ago on solaris machines, but I have not access to
solaris machines anymore. I do not mean limiting the
absolute CPU
Hello, (maybe a FAQ, but could not find this question)
is it possible with linux2.4 to limit the relative CPU time
per process or per UID? I saw something like this about 5
years ago on solaris machines, but I have not access to
solaris machines anymore. I do not mean limiting the
absolute CPU
sshd is
at nice 0.
Xun.
Any other ideas or will I get hacking..
Padraig.
Xuan Baldauf wrote:
Hello, (maybe a FAQ, but could not find this question)
is it possible with linux2.4 to limit the relative CPU time
per process or per UID? I saw something like this about 5
years ago
Resent patch, hope that it will be acknowledged or discussed.
Xuân. :o)
Hello,
I discovered a bug in netfilter and worked the last 4 days to track it
down (I'm not a kernel hacker...):
Symptoms:
"Sometimes" the ip_conntrack module won't unload. rmmod or modprobe -r
would stay unkillably
Resent patch, hope that it will be acknowledged or discussed.
Xuân. :o)
Hello,
I discovered a bug in netfilter and worked the last 4 days to track it
down (I'm not a kernel hacker...):
Symptoms:
"Sometimes" the ip_conntrack module won't unload. rmmod or modprobe -r
would stay unkillably
is algorithm as
his|her breakfast
instead of waiting for me to do that. :o)
Xuân.
>
>
> Hans
>
> Ragnar Kjørstad wrote:
> >
> > On Sat, Sep 16, 2000 at 01:17:53PM +0200, Xuan Baldauf wrote:
> > > I'm not a kernel hacker (and therefore I'm not familiar with th
Ragnar Kjørstad wrote:
On Sat, Sep 16, 2000 at 01:17:53PM +0200, Xuan Baldauf wrote:
I'm not a kernel hacker (and therefore I'm not familiar with the kernel
terminology), and maybe this idea is already old, but here is an
algorithm for an elevator which tries to guarantee smoothness
"Ragnar Kjørstad" wrote:
> On Sat, Sep 16, 2000 at 01:17:53PM +0200, Xuan Baldauf wrote:
> > I'm not a kernel hacker (and therefore I'm not familiar with the kernel
> > terminology), and maybe this idea is already old, but here is an
> > algorithm for an el
Hello,
I'm not a kernel hacker (and therefore I'm not familiar with the kernel
terminology), and maybe this idea is already old, but here is an
algorithm for an elevator which tries to guarantee smoothness and no
stalling:
Every rw-request gets an expiry timeout (e.g. in jiffies) where it's
Hello,
I'm not a kernel hacker (and therefore I'm not familiar with the kernel
terminology), and maybe this idea is already old, but here is an
algorithm for an elevator which tries to guarantee smoothness and no
stalling:
Every rw-request gets an expiry timeout (e.g. in jiffies) where it's
38 matches
Mail list logo
