From: Christopher Faylor <cgf@redhat.com>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: overseers@sources.redhat.com
Subject: Re: DB2 problem...: PANIC: No space left on device
Date: Wed, 28 Mar 2001 16:08:00 -0000 [thread overview]
Message-ID: <20010328190840.B3389@redhat.com> (raw)
Message-ID: <20010328160800.tf77FhygeOPB0SfPXUtrUvCWmrM_Lbq5yWQMc2MPLQI@z> (raw)
In-Reply-To: <Pine.BSF.4.30.0103281800440.7123-100000@dair.pair.com>
On Wed, Mar 28, 2001 at 06:28:58PM -0500, Hans-Peter Nilsson wrote:
>On Mon, 26 Mar 2001, Jason Molenda wrote:
>
>> On Sun, Mar 25, 2001 at 11:42:58PM -0500, Hans-Peter Nilsson wrote:
>> >
>> > In other words: can there please be some more disk for htdig use?
>> >
>>
>> It seems that /dev/hda4 is the partition that we were talking about
>> mounting on /gcc/htdig. Is there some reason not to mount this?
>> If it's available and writable by user htdig, I'm sure either H-P
>> or I will find the time to do the rest.
>
>Yes.
>
>Sourceware is now spending >2 hours compressing and decompressing files
>*only* and still won't do better than an incomplete search database.
>That seems unnecessarily bad.
>
>If there's a root person listening, but who do not at this time want to
>get /dev/hda4 working (or similar thingy) please consider doing something
>like the following:
>
> mkdir /sourceware/snapshot-tmp/htdig-tmp
> chown htdigid:htdig /sourceware/snapshot-tmp/htdig-tmp
I've done this.
I don't remember discussing /dev/hda4. It is a 15GB partition. Do we
really need that much space? Will it help to have that much space or will
the above change be sufficient?
cgf
next prev parent reply other threads:[~2001-03-28 16:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-31 19:40 Hans-Peter Nilsson
2001-03-25 20:43 ` Hans-Peter Nilsson
2001-12-31 19:40 ` Jason Molenda
2001-03-26 2:05 ` Jason Molenda
2001-12-31 19:40 ` Hans-Peter Nilsson
2001-03-28 15:29 ` Hans-Peter Nilsson
2001-12-31 19:40 ` Christopher Faylor [this message]
2001-03-28 16:08 ` Christopher Faylor
2001-12-31 19:40 ` Jason Molenda
2001-03-28 16:22 ` Jason Molenda
2001-12-31 19:40 ` Christopher Faylor
2001-03-28 16:40 ` Christopher Faylor
2001-12-31 19:40 ` Christopher Faylor
2001-03-28 17:33 ` Christopher Faylor
2001-12-31 19:40 ` Jason Molenda
2001-03-28 17:40 ` Jason Molenda
2001-12-31 19:40 ` Christopher Faylor
2001-03-28 17:54 ` Christopher Faylor
2001-12-31 19:40 ` Christopher Faylor
2001-03-28 18:02 ` Christopher Faylor
2001-12-31 19:40 ` Frank Ch. Eigler
2001-03-28 18:14 ` Frank Ch. Eigler
2001-12-31 19:40 ` Hans-Peter Nilsson
2001-04-01 12:21 ` Hans-Peter Nilsson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010328190840.B3389@redhat.com \
--to=cgf@redhat.com \
--cc=hp@bitrange.com \
--cc=overseers@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).