On Thu, Dec 4, 2008 at 12:55 AM, Dan Nelson [EMAIL PROTECTED] wrote:
In the last episode (Dec 03), Vlad GALU said:
On Wed, Dec 3, 2008 at 8:56 PM, Dan Nelson [EMAIL PROTECTED] wrote:
[...]
Am I doing something wrong? I've applied the full diff, rebuilt
truss, now I get this:
-- cut here
/boot/kernel is ~118 MB on my system (including debugging symbols).
Default size of the root partition created by sysinstall is 512 MB, in your
case downsized to 360 to accomodate other partitions on your 8GB disk.
Should still be enough though. Do you have any other big files hanging
around in
Might be helpful to remember that /root is on /, so if you're in the
habit of leaving stuff in /root for doing sysadmin tasks, it can kill
/ pretty quickly...
On 2008-12-04 10:08:59AM +0100, Ruben de Groot wrote:
/boot/kernel is ~118 MB on my system (including debugging symbols).
Default
My backup script split filesystem dumps to files with size of 4,37 GB (4
588 544 kB). It's just an optimal size to fill out DVDs. At this moment
I have to burn them from windows via smb-link becuase I didn't manage to
do this task from FreeBSD console due to 2GB/4GB filesize restrictions
I've just realized that I see in releng/7 something that I did not see
in releng/6 - even if I use a file with custom rules in firewall_type I
still get default loopback rules installed.
I think that this is not correct, I am using custom rules exactly
because I want to control *everything* (e.g.
We have a production server which keeps crashing.
Hardware: two Quad Core Xeons (5420), 8GB ECC ram, Intel S5000
motherboard, Areca 1680-ix12 RAID card.
The memory have been replaced three times. Memtest runs OK. The
motherboard was replaced, all firmwares updated to the latest version
On Thu, Dec 04, 2008 at 07:15:05AM +, Bruce M. Simpson wrote:
Hi,
The inode size for the ext3 filesystem which Gentoo created for my last
install defaulted to 256 bytes, so I got bit by this problem.
I can't speak for the write path. but the read path looks just fine to
me, and the
On Thu, Dec 04, 2008 at 08:12:45AM +0100, Frode Nordahl wrote:
On 3. des.. 2008, at 20.43, Kostik Belousov wrote:
On Wed, Dec 03, 2008 at 08:12:22PM +0100, Frode Nordahl wrote:
(moved to freebsd-stable)
On 3. des.. 2008, at 18.39, Kostik Belousov wrote:
db where
Tracing pid 4 tid
On 4. des.. 2008, at 13.07, Kostik Belousov wrote:
On Thu, Dec 04, 2008 at 08:12:45AM +0100, Frode Nordahl wrote:
Got it!
panic: dqget: free dquot isn't dq=0xff00b3d27000
(kgdb) p/x *(struct dquot *)0xff00b3d27000
$1 = {dq_hash = {le_next = 0x0, le_prev = 0xff010b9da700},
On Thu, 04 Dec 2008 10:48:54 +0100
Bartosz Stec [EMAIL PROTECTED] wrote:
My backup script split filesystem dumps to files with size of 4,37 GB (4
588 544 kB). It's just an optimal size to fill out DVDs. At this moment
I have to burn them from windows via smb-link becuase I didn't manage to
Philipp Ost pisze:
Hi,
Bartosz Stec wrote:
[...] Is there *any* way to burn DVDs with files4GB from FreeBSD
console?
I succesfully used growisofs for exactly this task ;-)
What I did is (for DL-DVDs):
# growisofs -dvd-compat -Z /dev/cd0=$file.iso -speed=2
I had to limit the speed, else it
Kostik Belousov wrote:
...
Bruce, feel free to commit the patch.
I do not want to spend time on ext2 in any form, and due to our (only
partly jokingly) rule of the last committer is the owner, I do not
want to analyze ext2 bug reports after.
Yes, development resource is limited here
Hi,
Bartosz Stec wrote:
[...] Is there *any* way to
burn DVDs with files4GB from FreeBSD console?
I succesfully used growisofs for exactly this task ;-)
What I did is (for DL-DVDs):
# growisofs -dvd-compat -Z /dev/cd0=$file.iso -speed=2
I had to limit the speed, else it wouldn't do
problem is fixed in OpenBSD 4.4
http://www.openbsd.org/plus44.html
/Vladimir Ermakov
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
On Thursday 04 December 2008 16:24:23 Vladimir Ermakov wrote:
problem is fixed in OpenBSD 4.4
http://www.openbsd.org/plus44.html
The bug this note refers to was introduced after OpenBSD 4.1 (our last import)
and should not be present in the FreeBSD code. I'll double check in a bit to
make
On Thu, Dec 04, 2008 at 10:48:54AM +0100, Bartosz Stec wrote:
My backup script split filesystem dumps to files with size of 4,37 GB (4
588 544 kB). It's just an optimal size to fill out DVDs. At this moment
I have to burn them from windows via smb-link becuase I didn't manage to
do this
David Kelly wrote:
On Thu, Dec 04, 2008 at 10:48:54AM +0100, Bartosz Stec wrote:
My backup script split filesystem dumps to files with size of 4,37 GB (4
588 544 kB). It's just an optimal size to fill out DVDs. At this moment
I have to burn them from windows via smb-link becuase I didn't
Could you please point me to your patch and an explanation on how to apply it
and test it?
You can grab the patch here:
http://pflog.net/~floyd/ext2fs.diff
To apply it:
cd /usr/src/sys/gnu/fs
patch /path/to/ext2fs.diff
cd /usr/src/sys/modules/ext2fs
make clean make
kldload ./ext2fs.ko
On Wednesday 03 December 2008 8:53:43 pm Josh Carroll wrote:
Ok, I describe my concern once more. I do not object against the checking
of the inode size. But, if inode size is changed, then some data is added
to the inode, that could (and usually does, otherwise why extend it ?)
change
On Thursday 04 December 2008 16:47:13 Max Laier wrote:
On Thursday 04 December 2008 16:24:23 Vladimir Ermakov wrote:
problem is fixed in OpenBSD 4.4
http://www.openbsd.org/plus44.html
The bug this note refers to was introduced after OpenBSD 4.1 (our last
import) and should not be present
Not too say you're .iso images can't be 2GB/4GB, but I'm pretty sure
the ISO9660 standard is limited to a 2GB maximum file size (for files
within the .iso). You must use UDF to burn files of greater size.
mkisofs(8) seems to support this, if only in alpha/hybrid stage:
-udf Include
on 28/11/2008 16:28 Andriy Gapon said the following:
uname:
FreeBSD 7.1-PRERELEASE r185311 amd64
dmesg:
ichwd0: Intel ICH9R watchdog timer on isa0
ichwd0: Intel ICH9R watchdog timer (ICH9 or equivalent)
ichwd0: timer disabled
pciconf:
[EMAIL PROTECTED]:0:31:0: class=0x060100
On 2008-Dec-03 15:42:04 +0900, Nathan Butcher [EMAIL PROTECTED] wrote:
Automatic labelling on 7.0 created about 360MB for my root partition on
a 8GB disk. After a buildkernel into 7.1-PRERELEASE, the root partition
was exhausted during the installkernel.
Are you running i386 or amd64? 360MB _is_
On Thu, Dec 04, 2008 at 12:44:14PM -0500, Steve Polyack wrote:
Not too say you're .iso images can't be 2GB/4GB, but I'm pretty sure
the ISO9660 standard is limited to a 2GB maximum file size (for files
within the .iso). You must use UDF to burn files of greater size.
mkisofs(8) seems to
Date: Tue, 2 Dec 2008 19:33:00 +0300
From: Alexandr Pakhomov [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
On Tue, Dec 2, 2008 at 5:12 PM, Mike Tancsa [EMAIL PROTECTED] wrote:
At 08:38 AM 12/2/2008, Kostik Belousov wrote:
mdconfig -a -t malloc -s 1800M
You cannot have ~ 2Gb of
Kevin Oberman wrote:
Date: Tue, 2 Dec 2008 19:33:00 +0300
From: Alexandr Pakhomov [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
On Tue, Dec 2, 2008 at 5:12 PM, Mike Tancsa [EMAIL PROTECTED] wrote:
At 08:38 AM 12/2/2008, Kostik Belousov wrote:
mdconfig -a -t malloc -s 1800M
It seems that the term swap-backed is misleading for some people. It does
NOT mean your md(4) device will be constantly swapping to disk (and the man
page does an alright job of relaying this). It simply means that generally
available memory will be used, and so will swap iff available
I've got an HP DL-360 1U here that has a slim SATA CDROM. I've (so far)
tried booting FreeBSD-7.0-RELEASE and FreeBSD-7.1-BETA2. I've tried both
rewritable media (my first choice) and write-once media. The kernel loads
fine, but multiuser fails with acd0: TIMEOUT - READ_BIG retrying ...
twice,
Date: Thu, 4 Dec 2008 17:11:46 -0500
From: Josh Carroll [EMAIL PROTECTED]
It seems that the term swap-backed is misleading for some people. It does
NOT mean your md(4) device will be constantly swapping to disk (and the man
page does an alright job of relaying this). It simply means
On 12/4/08, Bartosz Stec [EMAIL PROTECTED] wrote:
Philipp Ost pisze:
Hi,
Bartosz Stec wrote:
[...] Is there *any* way to burn DVDs with files4GB from FreeBSD
console?
I succesfully used growisofs for exactly this task ;-)
What I did is (for DL-DVDs):
# growisofs -dvd-compat -Z
Hi,
Apparently 7.1-PRERELEASE has been pulled from freebsd-update's server
while I was being lazy:
calvin% sudo freebsd-update --debug upgrade -r 7.1-BETA2
Looking up update.FreeBSD.org mirrors... 1 mirrors found.
Fetching metadata signature for 7.1-PRERELEASE from
update1.FreeBSD.org...
fetch:
On 05/12/2008, at 12:14 PM, Joan Picanyol i Puig wrote:
Hi,
Apparently 7.1-PRERELEASE has been pulled from freebsd-update's server
while I was being lazy:
calvin% sudo freebsd-update --debug upgrade -r 7.1-BETA2
Looking up update.FreeBSD.org mirrors... 1 mirrors found.
Fetching metadata
Are you running i386 or amd64? 360MB _is_ a very tight fit for amd64
but you should make it unless you have some large, unexpected files
lying around in your root partition. As a workaround, you could
remove *.symbols from the old kernel files.
Running amd64. The install was fresh so there
* Max Laier [EMAIL PROTECTED] [2008-12-04 18:28:33 +0100]:
On Thursday 04 December 2008 16:47:13 Max Laier wrote:
On Thursday 04 December 2008 16:24:23 Vladimir Ermakov wrote:
problem is fixed in OpenBSD 4.4
http://www.openbsd.org/plus44.html
The bug this note refers to was
Hi
I'm getting some strange messages:
Dec 5 07:49:19 jonny kernel: rtfree: 0xff0001379d90 has 1 refs
Dec 5 07:49:19 jonny kernel: rtfree: 0xff000a1784d8 has 1 refs
Dec 5 07:49:28 jonny kernel: rtfree: 0xff000198a7c0 has 1 refs
Dec 5 07:49:31 jonny kernel: rtfree:
Max Laier wrote:
Okay ... here is the story: First off, synproxy state is *NOT* broken! But
you need to be careful how you use it. If you - like the OP - intend to use
it to protect a service running on the same box as your pf, you must make sure
to set skip on lo0 or it will not work.
36 matches
Mail list logo
