On Mon, 25 Sep 2006, Dag-Erling Sm?rgrav wrote:
DS> > > > My experiments show that if you have enough memory to host radmdrive
for
DS> > > > /usr/src you'd better leave it for caching - there were no
statistically
DS> > > > meaningful performance difference, at least on machines with 1G+ RAM.
DS
> > Maybe I can mount a dirty partition. I just need the data off it...
> Mount it read-only and get the data off it IMMEDIATELY. I wouldn't try
> fsck-ing on any disk with even a single read or write error. Fsck will
> fail if it can't find a real sector to allocate, and I don't think it d
Can someone point me to a fairly detailed description of
how softdep handles "rm", in particular how it determines
whether a particular inode (e.g. a symlink) contains text
instead of a list of block numbers?
___
freebsd-hackers@freebsd.org mailing li
Thanks
At 02:53 PM 9/25/2006, you wrote:
On Mon, Sep 25, 2006 at 02:41:18PM -0600, [EMAIL PROTECTED] wrote:
>
> Maybe I can mount a dirty partition. I just need the data off it...
Mount it read-only and get the data off it IMMEDIATELY. I wouldn't try
fsck-ing on any disk with even
On Mon, Sep 25, 2006 at 02:41:18PM -0600, [EMAIL PROTECTED] wrote:
>
> Maybe I can mount a dirty partition. I just need the data off it...
Mount it read-only and get the data off it IMMEDIATELY. I wouldn't try
fsck-ing on any disk with even a single read or write error. Fsck will
fail if it
Hi Peter,
The hard drive is in the fridge right now, in case it's a heat problem.
It's FreeBSD version 4.x. It's getting hard read errors, and I'm using -y
with fsck so it will continue on to the next error without prompting from
me. The same thing happens whether I use the -y flag or not. I
Oliver Fromme wrote:
> Eric Anderson wrote:
> > Oliver Fromme wrote:
> > > Reading /usr/src from a physical disk certainly requires
> > > quite some I/O that takes more than zero time.
> >
> > But, in order to populate the ram disk, you must read /usr/src also from
> > something, and that also ta
I've got a /usr partition with some problems. During boot it fails and I'm
prompted to run fsck manually. I do so and when fsck has finished it asks
me to run it again, and again, and again...it seems to find the same errors
each time. It never seems to repair anything. It worked fine on errors it
On Mon, 2006-Sep-25 12:38:47 -0600, [EMAIL PROTECTED] wrote:
>I've got a /usr partition with some problems. During boot it fails and I'm
>prompted to run fsck manually. I do so and when fsck has finished it asks
>me to run it again, and again, and again...it seems to find the same errors
>each t
I've got a /usr partition with some problems. During boot it fails and I'm
prompted to run fsck manually. I do so and when fsck has finished it asks
me to run it again, and again, and again...it seems to find the same errors
each time. It never seems to repair anything. It worked fine on err
Borja Marcos wrote:
Hello,
I saw this some time ago but always forgot to report it.
I'm running a pair of machines with FreeBSD/sparc64 (various versions,
one of them is running -STABLE now), and I've seen a problem with the
network stack.
Looking at buffer and window sizes,
earendil# sysc
Hello,
I saw this some time ago but always forgot to report it.
I'm running a pair of machines with FreeBSD/sparc64 (various
versions, one of them is running -STABLE now), and I've seen a
problem with the network stack.
Looking at buffer and window sizes,
earendil# sysctl net.inet.tcp|fgr
Dmitry Morozovsky <[EMAIL PROTECTED]> writes:
> Kris Kennaway <[EMAIL PROTECTED]> wrote:
> > Dmitry Morozovsky <[EMAIL PROTECTED]> writes:
> > > My experiments show that if you have enough memory to host radmdrive for
> > > /usr/src you'd better leave it for caching - there were no statistically
>
13 matches
Mail list logo
