On Tue, 23 Aug 2005, Fafa Hafiz Krantz wrote:
>
> hello!
>
> how come *nothing* happens when i rm -rf directory/?
> it just won't move ...
>
> top from another terminal tells me:
> 55272 root 1160 14396K 13768K RUN 0:27 36.13% 35.40% rm
>
> what? the directory/ only contains a .maildi
On Mon, 22 Aug 2005, Danial Thom wrote:
> A more important question is: why did you "order
> a whole bunch of servers" without testing one
> first? A curious approach to computing.
>
> DT
We weren't made aware that the newer servers were coming with a later rev
board, and a customer came along as
I wasn't able to find anything about this on Google unfortunately. Hoping
that if this thread can determine the problem, others will be able to find
it.
We ordered a whole batch of servers which have the IPMI 2.0 board (I am
pretty sure). When they first come online they seem to have the MAC
00:30
On Wed, 17 Aug 2005, Jorge Mario G. Mazo wrote:
> hi there
> I've been looking for a way to check the fs type
> I need to do something like this
>
> if NTFS do this
> if msdis do that
> if ufs2 do that
> if ext2 do this other stuff
>
> thanks in advance
I'd check out the fdisk code. For example:
On Tue, 16 Aug 2005, Nikolas Britton wrote:
> 4.x compared to 5.x will always be more stable
> 5.x compared to 6.x will always be more stable
> 6.x compared to 7.x will al
>
> Do you see a trend? 4.x works now but what about in another year, two
> years, or three?
I expect it should work just
On Tue, 16 Aug 2005, dpk wrote:
> On Tue, 16 Aug 2005, Carstea Catalin wrote:
>
> > what version of freebsd do u recomand for a stable server?
>
> 4.11 is solid, hasn't shown any problems here. 5.4 is the best of the 5.x
> series but we (I mean at my company, not
On Tue, 16 Aug 2005, Carstea Catalin wrote:
> what version of freebsd do u recomand for a stable server?
4.11 is solid, hasn't shown any problems here. 5.4 is the best of the 5.x
series but we (I mean at my company, not speaking as a FreeBSD rep)
haven't put it through as much stress as we have 4
On Fri, 12 Aug 2005, Greg Barniskis wrote:
> It can be argued (and has been, a lot) whether the hardware problems
> that some folks clearly do have are the fault of the hardware or of
> the new FreeBSD architecture. Myself, I think it's probably a little
> of each. Even though the hardware in ques
On Fri, 12 Aug 2005, Xu Qiang wrote:
> This is my test script:
>
> -
> #!/bin/bash
>
> var=0
> var=$[3]
>
> vari=0
> ++vari
>
> echo $var
> echo $vari
> -
>
> The result is:
> ./test.sh: ++vari: command not found
> 3
> 0
>
> So the manual of bash is incorrec
On Fri, 12 Aug 2005, Xu Qiang wrote:
> Hi, all:
>
> I don't know if this is the right list to ask this question. But since I
> didn't find a bash script mail list and you guys are always so helpful,
> then...
>
> Here are an excerpt of a bash script:
>
> ---
On Thu, 11 Aug 2005, Randy Schultz wrote:
> Hey all,
>
> Is there any documentation on wizard mode? I'm just wondering what the
> scan function does.
Looking at the source, I would guess that it counts how many 512 byte
blocks there are on a device. It prints B: at the beginning and G: at the
en
On Fri, 12 Aug 2005, Hexren wrote:
> The next time that happens try ^C.
> If the startup process hangs in bringing up a daemon you cann kill
> that like any other foreground running process. Maybe that was what
> hit you at least it sound a lot like that to me.
>
> Hexren
Also, try ^T. ^T should
On Thu, 11 Aug 2005, Eric Lance wrote:
> Hello all,
>
> I just finished installing FreeBSD 5.4 on my PC. When i boot it
> normally all of the startup scripts finish, no errors are displayed but
> afterwards a login prompt fails to appear. If i boot in single user mode
> I get my '#' prompt right
On Wed, 10 Aug 2005, Valerio daelli wrote:
> Hi all
> does anyone know any maximum limit to the slice size in freebsd?
> We would like to create a filesystem of 2.2T.
> Is there any limit in fdisk and bsdlabel?
> Thanks a lot
fdisk does not support >2TB partitions -- at least, I've been unable to
On Tue, 2 Aug 2005, dpk wrote:
> (Another panic I would get would follow roughly the same path except it
> would die while trying to unlock a vnode lock that the thread didn't own.
> I'll try to get this information some time, too.)
Here's the backtrace from that panic:
After much struggling (documented elsewhere) I have a backtrace showing
one of a handful of panics I am getting on a FreeBSD 5.4-RELEASE-p5
system. The server has 4GB RAM, and is running with PAE and SMP enabled.
If this is not the appropriate list for this, I can send it elsewhere,
please let me k
Sorry for all the questions to the list, we're having a number of issues
deploying FreeBSD 5.4 and we're trying to get an understanding of what
we're seeing.
When I reboot these servers (using "reboot" on the command line), it will
go through the usual routine I'm familiar with from FreeBSD 4.x, b
I'm getting some panics on a few FreeBSD 5.4 boxes, and I'm trying to
figure out a way to get them to drop to some sort of debugger, or to dump
core. It used to be that you'd just add:
options DDB
options DDB_UNATTENDED
and build a kernel with -g, set 'dumpon', and then when it paniced it
would w
The resolution to this problem turned out to be enabling the 3Ware 9500S
"auto carving" option. This splits all partitions into 2TB chunks, which
are then presented to the OS as separate LUNs.
FreeBSD 5.4-RELEASE's driver for the 3Ware card does not support multiple
LUNs, but the new driver (Commo
On Fri, 29 Jul 2005, Giorgos Keramidas wrote:
> Hmmm, in multiuser mode, your root filesystem is mounted as read-write
> and it resides in da0, so GEOM will forbid opening the disk device in
> read-write mode for editing the partition table.
>
> In single user mode, devfs is still used, but your r
On Thu, 28 Jul 2005, dpk wrote:
> truss indicates that fdisk may be getting the error from somewhere else:
>
> stat("/dev/da0",0xbfbfeb30) = 0 (0x0)
> open("/dev/da0",0x2,00) ERR#1 'Operation not
> permi
On Fri, 29 Jul 2005, Giorgos Keramidas wrote:
> It won't wipe away the table. It will just let you edit the existing
> table interactively, through a series of questions like:
>
> - Do you want to edit partition 1?
> - Do you want to edit partition 2?
> - Do you want to edit par
On Thu, 21 Jul 2005, Giorgos Keramidas wrote:
> Are you trying to start from scratch, or just making changes to the
> existing table? If it's the second, then try the -u option:
>
> # fdisk -u /dev/da0
>
> This should give you a chance to interactively change the partition
> table of the di
Woah. Well, I guess I didn't try *everything*. Removing "device acpi" from
the kernel config leaves me witih a PAE+SMP kernel that works fine. I can
fetch files at wire speed and everything.
So, I guess this issue is closed. acpi was the ultimate culprit.
On Thu, 28 Jul 2005, d
By the way, I also compared GENERIC performance against GENERIC w/
"options SMP" added, and had the same results.
On Wed, 27 Jul 2005, dpk wrote:
> We just received several SuperMicro servers, 3.0Ghz Xeon x 2, 4GB RAM.
> They're using the em driver and the ports are set
We just received several SuperMicro servers, 3.0Ghz Xeon x 2, 4GB RAM.
They're using the em driver and the ports are set to 1000Mbit (we also
tried 100Mbit/full duplex on the card and on the switch). They're running
FreeBSD 5.4.
I ran a steady ping on a couple of them while they were running "GENE
On Wed, 20 Jul 2005, Lowell Gilbert wrote:
> dpk <[EMAIL PROTECTED]> writes:
>
> > Has anyone here had any luck whatsoever getting FreeBSD 5.4-RELEASE to use
> > 4TB of space from a 4TB RAID array? It is apparent that there is a
> > 1TB/slice limit, and sysinst
Has anyone here had any luck whatsoever getting FreeBSD 5.4-RELEASE to use
4TB of space from a 4TB RAID array? It is apparent that there is a
1TB/slice limit, and sysinstall doesn't seem to be able to handle creating
more than 2 slices.
I read somewhere that people recommend using "gpt" to manage
We have various servers, with various versions of FreeBSD throwing these
NMI messages:
NMI ISA 3c, EISA ff
NMI ISA 2c, EISA ff
NMI ISA 20, EISA ff
There's no information about this anywhere that I can see, but at least
two other people have had the problem according to Google searches.
If tripwi
n't
> rely on top too much acually. Vmstat is a better program when looking
> at memory.
>
> Cheers,
>
> Jorn
> - Original Message -
> From: "dpk" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Saturday, January 31, 2004 1:10 AM
>
ose this problem,
or any programs I can run to try and track this stray memory use down?
- dpk
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
31 matches
Mail list logo
