VIA 8237 RAID

2005-06-30 Thread Franco Bruno Borghesi 
Has anyone tried any VIA 8237 RAID motherboard?

I've just bought a MSI K8T Neo with 2x80GB SATA 150 disks. I've created a 
Raid 1 configuration from the BIOS, but when FreeBSD (5.4 for x86) CD boots 
it detects both disks (ad4, ad6) and installer allows me to partition both 
disks individually.

I was hopping to see a single 80 GB drive from BSD. Could anyone give a 
hint?

Thanks in advance.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Installing on multiple machines

2005-05-24 Thread Franco Bruno Borghesi 
You could use freebsd livecd (http://livecd.sourceforge.net/) for multiple 
installations. I don't know what kickstart is, but livecd lets you build an 
installation cd from an existing installation, and replicate it on other 
machines.

24 May 2005 14:25:16 -0400, Lowell Gilbert <
[EMAIL PROTECTED]>:
> 
> Ewald Jenisch <[EMAIL PROTECTED]> writes:
> 
> > I'd like to install 5.4 on several machines. The hardware is similar,
> > but not exactly equal (different size HDs, different amount of
> > memory).
> >
> > Is there any way to install 5.4 on different machines with the same
> > options, i.e. same set of packages, same settings (e.g. keyboard)
> > etc. without manually going through the installation on every machine?
> >
> > What I'm thinking of is something similar to the "kickstart" feature
> > in Linux.
> >
> > Is there anything similar under FreeBSD available?
> 
> I'm not much of an expert on FreeBSD installs, and I know even less
> about Linux installs, but seeing that no one else has spoken up, I can
> at least point you in a few relevant directions.
> 
> First of all, the standard install is scriptable to some extent. The
> manual for sysinstall(8) documents this capability. There are some
> messages in the archives of this list discussing people doing that.
> 
> Another option is Freesbie, which has recently gained the ability to
> install to hard disk.
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
> [EMAIL PROTECTED]"
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Top only showing one active CPU on HTT system

2005-05-24 Thread Franco Bruno Borghesi 
I'm curious... doesn't enabling ht make your system run slower? That's what 
I had found searching on google a while ago, and that's why I have never 
enabled ht on my kernels.


2005/5/24, Kirk Strauser <[EMAIL PROTECTED]>:
> 
> On Tuesday 24 May 2005 10:59, Tim Kellers wrote:
> 
> > The acpi_load="YES" in /boot/loader.conf might do the trick.
> 
> Actually, it turns out that I have to set machdep.hyperthreading_allowed=1
> for HTT to work now.
> 
> Speaking of which, is that tunable documented anywhere besides the HTT
> security PR? It's not in the 5.4-STABLE /usr/src/UPDATING or anyplace else
> I've looked, so I was more than a bit surprised to find that such an
> important default was changed without much notice. I imagine a lot of
> people read the PR much as I did: "blah, blah, theoretical, doesn't affect
> me, next message"...
> --
> Kirk Strauser
> 
> 
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 3Ware SATA RAID 8000 - Supported on 5.3-R?

2005-05-24 Thread Franco Bruno Borghesi 
Yes, but the default value is "NO".

If you still have problems, ask again.

2005/5/24, Jonathan M. Slivko <[EMAIL PROTECTED]>:
> 
> OK, I added that. (it was actually already in /etc/defaults/rc.conf)
> -- Jonathan
> 
> Franco Bruno Borghesi wrote:
> > If it fails it's because there are certain inconsistencies that need
> > user confirmation before they are corrected.
> >
> > You can add
> > fsck_y_enable="YES"
> > to your /etc/rc.conf so if default fsck fails, fsck -y is run. Check the
> > fsck man page before doing so.
> >
> > Anyway, I don't understand why fsck is run on every reboot. If you just
> > try a "reboot" or a "shutdown -r now" command in your console, will fsck
> > run next time the system boots? It should'n happen. I don't understand
> > why your file systems get uncleanly umounted.
> >
> > About freebsd 5.3, I've been using 3ware 7500-4LP (in raid 5) for the
> > last 3 months, and I have not had such (nor any other) problems with twe
> > driver.
> >
> > Hope it helps.
> >
> > 2005/5/24, Jonathan M. Slivko <[EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]>>:
> >
> > Whether I run fsck manually or if I run it automagically at boot via rc
> > (which happens every reboot), it fails. As I'm not at console, I can't
> > tell whether the same things happen if the box is physically taken
> > down.
> > and fsck'd in single user mode. The better part of the question is,
> > could this be the RAID card throwing out false errors due to not having
> > complete support for 5.3-R?, as it says that it only supports the 4.x
> > series.
> >
> > -- Jonathan
> >
> > Franco Bruno Borghesi wrote:
> > > Your fstab is OK.
> > >
> > > I don't exactly understand the problem. When you boot fsck will run
> > > automatically if the system did not correctly shut down. This is
> > done
> > > *before* disks are mounted rw, so there's no way you will see the
> > "(NO
> > > WRITE)" message.
> > >
> > > If system was not correctly shut down, fsck will run, and it
> > *will* (and
> > > should) slow down system boot process.
> > >
> > > So, is it the problem that fsck is running *every* time you boot?
> > Or is
> > > it that you get this "(NO WRITE)" message when you run it manually?
> > >
> > >
> > > 2005/5/24, Jonathan M. Slivko < [EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]>
> > > <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>>:
> > >
> > > [EMAIL PROTECTED](~)% cat /etc/fstab
> > > #
> > Device Mountpoint FStype Options Dump
> > > Pass#
> > > /dev/twed0s1b
> > > none swap sw 0 0
> > > /dev/twed0s1a / ufs
> > > rw 1 1
> > > /dev/twed0s1g /home ufs
> > rw,userquota,groupquota
> > > 2 2
> > > /dev/twed0s1d /tmp ufs
> > > rw 2 2
> > > /dev/twed0s1e /usr ufs
> > > rw 2 2
> > > /dev/twed0s1f /var ufs
> > > rw 2 2
> > > /dev/acd0 /cdrom cd9660 ro,noauto
> > > 0 0
> > > none /proc
> > > procfs rw 0 0
> > > [EMAIL PROTECTED](~)%
> > >
> > >
> > > Franco Bruno Borghesi wrote:
> > > > Could you post your /etc/fstab?
> > > >
> > > > 2005/5/24, Jonathan M. Slivko < [EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]>
> > > <mailto:[EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]>> >:
> > > >
> > > >>Yes, this is actually the autoboot fsck thats breaking,
> > the one
> > > that is
> > > >>called from /etc/rc (via /etc/rc.d/). I can physically
> > take the
> > > box down
> > > >>and do an offline fsck of it and that works fine, it's
> > just when
> > > it's in
> > > >>multi-user mode thats the problem.
> > > >>
> > > >>-- Jonathan
> > > >>
> > > >>Franco Bruno Borghesi wrote:
> > > >>
> > > >>>For fsck to work (to actually correct any problems you
> > may have),
> > > >>>partitions should be umounted first. Are you sure you
> > have umounted
> > > >>>/dev/twed before running fsck?
> > > >>>
> > > >>>
> > > >>>2005/5/24, Jonathan M. Slivko < [EMAIL PROTECTED]
&g

Re: 3Ware SATA RAID 8000 - Supported on 5.3-R?

2005-05-24 Thread Franco Bruno Borghesi 
If it fails it's because there are certain inconsistencies that need user 
confirmation before they are corrected.

You can add 
fsck_y_enable="YES" 
to your /etc/rc.conf so if default fsck fails, fsck -y is run. Check the 
fsck man page before doing so.

Anyway, I don't understand why fsck is run on every reboot. If you just try 
a "reboot" or a "shutdown -r now" command in your console, will fsck run 
next time the system boots? It should'n happen. I don't understand why your 
file systems get uncleanly umounted.

About freebsd 5.3, I've been using 3ware 7500-4LP (in raid 5) for the last 3 
months, and I have not had such (nor any other) problems with twe driver.

Hope it helps.

2005/5/24, Jonathan M. Slivko <[EMAIL PROTECTED]>:
> 
> Whether I run fsck manually or if I run it automagically at boot via rc
> (which happens every reboot), it fails. As I'm not at console, I can't
> tell whether the same things happen if the box is physically taken down.
> and fsck'd in single user mode. The better part of the question is,
> could this be the RAID card throwing out false errors due to not having
> complete support for 5.3-R?, as it says that it only supports the 4.x
> series.
> 
> -- Jonathan
> 
> Franco Bruno Borghesi wrote:
> > Your fstab is OK.
> >
> > I don't exactly understand the problem. When you boot fsck will run
> > automatically if the system did not correctly shut down. This is done
> > *before* disks are mounted rw, so there's no way you will see the "(NO
> > WRITE)" message.
> >
> > If system was not correctly shut down, fsck will run, and it *will* (and
> > should) slow down system boot process.
> >
> > So, is it the problem that fsck is running *every* time you boot? Or is
> > it that you get this "(NO WRITE)" message when you run it manually?
> >
> >
> > 2005/5/24, Jonathan M. Slivko <[EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]>>:
> >
> > [EMAIL PROTECTED](~)% cat /etc/fstab
> > # Device Mountpoint FStype Options Dump
> > Pass#
> > /dev/twed0s1b
> > none swap sw 0 0
> > /dev/twed0s1a / ufs
> > rw 1 1
> > /dev/twed0s1g /home ufs rw,userquota,groupquota
> > 2 2
> > /dev/twed0s1d /tmp ufs
> > rw 2 2
> > /dev/twed0s1e /usr ufs
> > rw 2 2
> > /dev/twed0s1f /var ufs
> > rw 2 2
> > /dev/acd0 /cdrom cd9660 ro,noauto
> > 0 0
> > none /proc
> > procfs rw 0 0
> > [EMAIL PROTECTED](~)%
> >
> >
> > Franco Bruno Borghesi wrote:
> > > Could you post your /etc/fstab?
> > >
> > > 2005/5/24, Jonathan M. Slivko <[EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]> >:
> > >
> > >>Yes, this is actually the autoboot fsck thats breaking, the one
> > that is
> > >>called from /etc/rc (via /etc/rc.d/). I can physically take the
> > box down
> > >>and do an offline fsck of it and that works fine, it's just when
> > it's in
> > >>multi-user mode thats the problem.
> > >>
> > >>-- Jonathan
> > >>
> > >>Franco Bruno Borghesi wrote:
> > >>
> > >>>For fsck to work (to actually correct any problems you may have),
> > >>>partitions should be umounted first. Are you sure you have umounted
> > >>>/dev/twed before running fsck?
> > >>>
> > >>>
> > >>>2005/5/24, Jonathan M. Slivko < [EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]>
> > >>><mailto:[EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]>>>:
> > >>>
> > >>>Hello,
> > >>>
> > >>>I have an interesting question, I have a Pentium 4 2.4Ghz (No HT
> > >>>Enabled),
> > >>>2x80GB SATA Hard Drives in RAID 1. The box boots, works, etc.
> > However,
> > >>>whenever you try and do an fsck -y, it says:
> > >>>
> > >>>[EMAIL PROTECTED] (~)% fsck -y
> > >>>** /dev/twed0s1a (NO WRITE)
> > >>>** Last Mounted on /
> > >>>** Root file system
> > >>>** Phase 1 - Check Blocks and Sizes
> > >>>** Phase 2 - Check Pathnames
> > >>>** Phase 3 - Check Connectivity
> > >>>** Phase 4 - Check Reference Counts
> > >>>** Phase 5 - Check Cyl groups
> > >>>2821 files, 31805 used, 474682 free (322 frags, 59295 blocks, 0.1%
> > >>>fragmentation)
> > >>>
> > >>>** /dev/tw

Re: 3Ware SATA RAID 8000 - Supported on 5.3-R?

2005-05-24 Thread Franco Bruno Borghesi 
Your fstab is OK.

I don't exactly understand the problem. When you boot fsck will run 
automatically if the system did not correctly shut down. This is done 
*before* disks are mounted rw, so there's no way you will see the "(NO 
WRITE)" message.

If system was not correctly shut down, fsck will run, and it *will* (and 
should) slow down system boot process.

So, is it the problem that fsck is running *every* time you boot? Or is it 
that you get this "(NO WRITE)" message when you run it manually?


2005/5/24, Jonathan M. Slivko <[EMAIL PROTECTED]>:
> 
> [EMAIL PROTECTED](~)% cat /etc/fstab
> # Device Mountpoint FStype Options Dump
> Pass#
> /dev/twed0s1b none swap sw 0 0
> /dev/twed0s1a / ufs rw 1 1
> /dev/twed0s1g /home ufs rw,userquota,groupquota
> 2 2
> /dev/twed0s1d /tmp ufs rw 2 2
> /dev/twed0s1e /usr ufs rw 2 2
> /dev/twed0s1f /var ufs rw 2 2
> /dev/acd0 /cdrom cd9660 ro,noauto 0 0
> none /proc procfs rw 0 0
> [EMAIL PROTECTED](~)%
> 
> 
> Franco Bruno Borghesi wrote:
> > Could you post your /etc/fstab?
> >
> > 2005/5/24, Jonathan M. Slivko <[EMAIL PROTECTED]>:
> >
> >>Yes, this is actually the autoboot fsck thats breaking, the one that is
> >>called from /etc/rc (via /etc/rc.d/). I can physically take the box down
> >>and do an offline fsck of it and that works fine, it's just when it's in
> >>multi-user mode thats the problem.
> >>
> >>-- Jonathan
> >>
> >>Franco Bruno Borghesi wrote:
> >>
> >>>For fsck to work (to actually correct any problems you may have),
> >>>partitions should be umounted first. Are you sure you have umounted
> >>>/dev/twed before running fsck?
> >>>
> >>>
> >>>2005/5/24, Jonathan M. Slivko <[EMAIL PROTECTED]
> >>><mailto:[EMAIL PROTECTED]>>:
> >>>
> >>>Hello,
> >>>
> >>>I have an interesting question, I have a Pentium 4 2.4Ghz (No HT
> >>>Enabled),
> >>>2x80GB SATA Hard Drives in RAID 1. The box boots, works, etc. However,
> >>>whenever you try and do an fsck -y, it says:
> >>>
> >>>[EMAIL PROTECTED] (~)% fsck -y
> >>>** /dev/twed0s1a (NO WRITE)
> >>>** Last Mounted on /
> >>>** Root file system
> >>>** Phase 1 - Check Blocks and Sizes
> >>>** Phase 2 - Check Pathnames
> >>>** Phase 3 - Check Connectivity
> >>>** Phase 4 - Check Reference Counts
> >>>** Phase 5 - Check Cyl groups
> >>>2821 files, 31805 used, 474682 free (322 frags, 59295 blocks, 0.1%
> >>>fragmentation)
> >>>
> >>>** /dev/twed0s1g (NO WRITE)
> >>>** Last Mounted on /home
> >>>** Phase 1 - Check Blocks and Sizes
> >>>** Phase 2 - Check Pathnames
> >>>** Phase 3 - Check Connectivity
> >>>** Phase 4 - Check Reference Counts
> >>>** Phase 5 - Check Cyl groups
> >>>82057 files, 557735 used, 12912399 free (2343 frags, 1613757 blocks,
> >>>0.0%
> >>>fragmentation)
> >>>
> >>>** /dev/twed0s1d (NO WRITE)
> >>>** Last Mounted on /tmp
> >>>** Phase 1 - Check Blocks and Sizes
> >>>** Phase 2 - Check Pathnames
> >>>** Phase 3 - Check Connectivity
> >>>** Phase 4 - Check Reference Counts
> >>>** Phase 5 - Check Cyl groups
> >>>30 files, 1787 used, 504700 free (20 frags, 63085 blocks, 0.0%
> >>>fragmentation)
> >>>
> >>>** /dev/twed0s1e (NO WRITE)
> >>>** Last Mounted on /usr
> >>>** Phase 1 - Check Blocks and Sizes
> >>>** Phase 2 - Check Pathnames
> >>>** Phase 3 - Check Connectivity
> >>>** Phase 4 - Check Reference Counts
> >>>** Phase 5 - Check Cyl groups
> >>>251160 files, 1318908 used, 13912410 free (73346 frags, 1729883 blocks,
> >>>0.5% fragmentation)
> >>>
> >>>** /dev/twed0s1f (NO WRITE)
> >>>** Last Mounted on /var
> >>>** Phase 1 - Check Blocks and Sizes
> >>>** Phase 2 - Check Pathnames
> >>>** Phase 3 - Check Connectivity
> >>>** Phase 4 - Check Reference Counts
> >>>** Phase 5 - Check Cyl groups
> >>>4424 files, 63321 used, 7042830 free (2462 frags, 880046 blocks, 0.0%
> >>>fragmentation)
> >>>
> >>>The drives are Seagate SATA's (7200RPM) with a 3Ware SATA RAID
> >>>Controller
> >>>(8006-2LP) using the twe kernel driver.

Re: 3Ware SATA RAID 8000 - Supported on 5.3-R?

2005-05-24 Thread Franco Bruno Borghesi 
Could you post your /etc/fstab?

2005/5/24, Jonathan M. Slivko <[EMAIL PROTECTED]>:
> 
> Yes, this is actually the autoboot fsck thats breaking, the one that is
> called from /etc/rc (via /etc/rc.d/). I can physically take the box down
> and do an offline fsck of it and that works fine, it's just when it's in
> multi-user mode thats the problem.
> 
> -- Jonathan
> 
> Franco Bruno Borghesi wrote:
> > For fsck to work (to actually correct any problems you may have),
> > partitions should be umounted first. Are you sure you have umounted
> > /dev/twed before running fsck?
> >
> >
> > 2005/5/24, Jonathan M. Slivko <[EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]>>:
> >
> > Hello,
> >
> > I have an interesting question, I have a Pentium 4 2.4Ghz (No HT
> > Enabled),
> > 2x80GB SATA Hard Drives in RAID 1. The box boots, works, etc. However,
> > whenever you try and do an fsck -y, it says:
> >
> > [EMAIL PROTECTED] (~)% fsck -y
> > ** /dev/twed0s1a (NO WRITE)
> > ** Last Mounted on /
> > ** Root file system
> > ** Phase 1 - Check Blocks and Sizes
> > ** Phase 2 - Check Pathnames
> > ** Phase 3 - Check Connectivity
> > ** Phase 4 - Check Reference Counts
> > ** Phase 5 - Check Cyl groups
> > 2821 files, 31805 used, 474682 free (322 frags, 59295 blocks, 0.1%
> > fragmentation)
> >
> > ** /dev/twed0s1g (NO WRITE)
> > ** Last Mounted on /home
> > ** Phase 1 - Check Blocks and Sizes
> > ** Phase 2 - Check Pathnames
> > ** Phase 3 - Check Connectivity
> > ** Phase 4 - Check Reference Counts
> > ** Phase 5 - Check Cyl groups
> > 82057 files, 557735 used, 12912399 free (2343 frags, 1613757 blocks,
> > 0.0%
> > fragmentation)
> >
> > ** /dev/twed0s1d (NO WRITE)
> > ** Last Mounted on /tmp
> > ** Phase 1 - Check Blocks and Sizes
> > ** Phase 2 - Check Pathnames
> > ** Phase 3 - Check Connectivity
> > ** Phase 4 - Check Reference Counts
> > ** Phase 5 - Check Cyl groups
> > 30 files, 1787 used, 504700 free (20 frags, 63085 blocks, 0.0%
> > fragmentation)
> >
> > ** /dev/twed0s1e (NO WRITE)
> > ** Last Mounted on /usr
> > ** Phase 1 - Check Blocks and Sizes
> > ** Phase 2 - Check Pathnames
> > ** Phase 3 - Check Connectivity
> > ** Phase 4 - Check Reference Counts
> > ** Phase 5 - Check Cyl groups
> > 251160 files, 1318908 used, 13912410 free (73346 frags, 1729883 blocks,
> > 0.5% fragmentation)
> >
> > ** /dev/twed0s1f (NO WRITE)
> > ** Last Mounted on /var
> > ** Phase 1 - Check Blocks and Sizes
> > ** Phase 2 - Check Pathnames
> > ** Phase 3 - Check Connectivity
> > ** Phase 4 - Check Reference Counts
> > ** Phase 5 - Check Cyl groups
> > 4424 files, 63321 used, 7042830 free (2462 frags, 880046 blocks, 0.0%
> > fragmentation)
> >
> > The drives are Seagate SATA's (7200RPM) with a 3Ware SATA RAID
> > Controller
> > (8006-2LP) using the twe kernel driver. The drives themselves allow data
> > to be read to/written from them, but fsck will not work (and is hanging
> > things on boot).
> >
> > Anyone got any ideas? I looked at www.3ware.com <http://www.3ware.com>
> > <http://www.3ware.com> earlier and it says that
> > the 8006-2LP's support FreeBSD 4.x, but not 5.x - could this be a result
> > of that, seeing as otherwise the drives/RAID work fine (AFAIK, it could
> > not be and I'm just not sure how to test it).
> >
> > TIA,
> > -- Jonathan
> > ___
> > freebsd-questions@freebsd.org <mailto:freebsd-questions@freebsd.org>
> > mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > To unsubscribe, send any mail to "
> > [EMAIL PROTECTED]
> > <mailto:[EMAIL PROTECTED]>"
> >
> >
> 
> --
> Jonathan M. Slivko - [EMAIL PROTECTED]
> "Linux: The Choice for the GNU Generation"
> - http://www.linux.org/ -
> 
> Don't fear the penguin.
> .^.
> /V\
> /( )\
> ^^-^^
> He's here to help.
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: 3Ware SATA RAID 8000 - Supported on 5.3-R?

2005-05-24 Thread Franco Bruno Borghesi 
For fsck to work (to actually correct any problems you may have), partitions 
should be umounted first. Are you sure you have umounted /dev/twed 
before running fsck?


2005/5/24, Jonathan M. Slivko <[EMAIL PROTECTED]>:
> 
> Hello,
> 
> I have an interesting question, I have a Pentium 4 2.4Ghz (No HT Enabled),
> 2x80GB SATA Hard Drives in RAID 1. The box boots, works, etc. However,
> whenever you try and do an fsck -y, it says:
> 
> [EMAIL PROTECTED](~)% fsck -y
> ** /dev/twed0s1a (NO WRITE)
> ** Last Mounted on /
> ** Root file system
> ** Phase 1 - Check Blocks and Sizes
> ** Phase 2 - Check Pathnames
> ** Phase 3 - Check Connectivity
> ** Phase 4 - Check Reference Counts
> ** Phase 5 - Check Cyl groups
> 2821 files, 31805 used, 474682 free (322 frags, 59295 blocks, 0.1%
> fragmentation)
> 
> ** /dev/twed0s1g (NO WRITE)
> ** Last Mounted on /home
> ** Phase 1 - Check Blocks and Sizes
> ** Phase 2 - Check Pathnames
> ** Phase 3 - Check Connectivity
> ** Phase 4 - Check Reference Counts
> ** Phase 5 - Check Cyl groups
> 82057 files, 557735 used, 12912399 free (2343 frags, 1613757 blocks, 0.0%
> fragmentation)
> 
> ** /dev/twed0s1d (NO WRITE)
> ** Last Mounted on /tmp
> ** Phase 1 - Check Blocks and Sizes
> ** Phase 2 - Check Pathnames
> ** Phase 3 - Check Connectivity
> ** Phase 4 - Check Reference Counts
> ** Phase 5 - Check Cyl groups
> 30 files, 1787 used, 504700 free (20 frags, 63085 blocks, 0.0%fragmentation)
> 
> ** /dev/twed0s1e (NO WRITE)
> ** Last Mounted on /usr
> ** Phase 1 - Check Blocks and Sizes
> ** Phase 2 - Check Pathnames
> ** Phase 3 - Check Connectivity
> ** Phase 4 - Check Reference Counts
> ** Phase 5 - Check Cyl groups
> 251160 files, 1318908 used, 13912410 free (73346 frags, 1729883 blocks,
> 0.5% fragmentation)
> 
> ** /dev/twed0s1f (NO WRITE)
> ** Last Mounted on /var
> ** Phase 1 - Check Blocks and Sizes
> ** Phase 2 - Check Pathnames
> ** Phase 3 - Check Connectivity
> ** Phase 4 - Check Reference Counts
> ** Phase 5 - Check Cyl groups
> 4424 files, 63321 used, 7042830 free (2462 frags, 880046 blocks, 0.0%
> fragmentation)
> 
> The drives are Seagate SATA's (7200RPM) with a 3Ware SATA RAID Controller
> (8006-2LP) using the twe kernel driver. The drives themselves allow data
> to be read to/written from them, but fsck will not work (and is hanging
> things on boot).
> 
> Anyone got any ideas? I looked at www.3ware.com earlier 
> and it says that
> the 8006-2LP's support FreeBSD 4.x, but not 5.x - could this be a result
> of that, seeing as otherwise the drives/RAID work fine (AFAIK, it could
> not be and I'm just not sure how to test it).
> 
> TIA,
> -- Jonathan
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
> [EMAIL PROTECTED]"
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: swap space

2005-05-03 Thread Franco Bruno Borghesi 
Time to upgrade then ;-)

2005/5/3, Chris Knipe <[EMAIL PROTECTED]>:
> 
> 
> > PS: Is there a FreeBSD 5.4 stable version?
> 
> FreeBSD pyro.acme.com  5.4-STABLE FreeBSD 5.4-STABLE#0: 
> Wed Apr 27 15:51:43
> SAST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PYRO i386
> 
> Guess so :)
> 
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: swap space

2005-05-03 Thread Franco Bruno Borghesi 
Actually having a separated disk for swap should increase your performance.
But my opinion is that if you really need *all* the 40 GB of swap when your 
system's ram is 3 GB, you won't see the difference: most of the data your 
system needs is swapped out!

You could add a partition to your new disk (let's say 2 or 3 times the 
amount of ram), and leave the rest unpartitioned. You could use that extra 
space later for nightly backups, emergencies, etc. without loosing your 
performance gain.

Hope it helps.

PS: Is there a FreeBSD 5.4 stable version?


2005/5/3, Chris Knipe <[EMAIL PROTECTED]>:
> 
> Hi,
> 
> Simple question really... Can you ever have to much swap space?
> 
> We're sitting with quite a nifty P4 System with 1GB Ram. We will more than
> likely add another 2 or 3GB in the month to come as our applications 
> (mainly
> perl) are consuming vast amounts of memory and swap.
> 
> We made the mistake however of just allocating 512MB swap as we did not 
> know
> accurately at the time of installation what the resouce requires are going
> to be (especially not that it would be this high).
> 
> Obviously reinstalling the entire OS / Applications is not really a 
> option.
> We may want to install a dedicated 40GB just for swap... Would this be
> advisable, or will it actually slow the system down? And to what extend?
> 
> We're running FreeBSD 5.4-STABLE.
> 
> Thanks in advance.
> 
> --
> Chris.
> 
> I love deadlines. I especially love the whooshing sound they make as they
> fly by..." - Douglas Adams, 'Hitchhiker's Guide to the Galaxy'
> 
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "
> [EMAIL PROTECTED]"
>
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"