Re: FreeBSD 5.4 - filesystem full
Hi, What kind of applications are you running on the machine ? Are they mmap'ing files on the filesystem in quesiton (which one ?) ? AFAIR even if you delete a big file the disk space may not be reclaimed if a process still has the file open. If you reboot the machine or restart some of the applications, does the issue disappear ? Regards, Adrian. On Wed, Nov 12, 2008 at 1:05 PM, Varshavchick Alexander <[EMAIL PROTECTED]> wrote: > I have an old enough server with FreeBSD 5.4 which from time to time > complains about filesystem full. But the problem is that the partition in > question has about 15G free space and more than 1000 free inodes. Then > all by itself the error dissapears, only to be repeated several hours later. > What can it be and where to look? The server runs mainly apache and > sendmail, nothing special. > > Thanks and regards > > > Alexander Varshavchick, Metrocom Joint Stock Company > Phone: (812)718-3322, 718-3115(fax) > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > 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: [rofug] Re: (Fwd) mountroot>
Hi, Please use english. Try inserting the following in /boot/loader.conf: root_disk_unit=1 From loader(8): root_disk_unit If the code which detects the disk unit number for the root disk is confused, eg. by a mix of SCSI and IDE disks, or IDE disks with gaps in the sequence (eg. no primary slave), the unit number can be forced by setting this variable. Alternatively you can try creating a file "boot.config" in the root filesystem containting: 2:da(1,a)/kernel See boot(8). Ady (@freebsd.ady.ro) On Sat, 21 Jun 2003, Camelia Nastase wrote: > > > 1. pe mine personal ma enerveaza cross-posting'ul. > 2. ai incercat cu boot -c, unload, boot-conf ? sau un ls dupa unload, sau > lsdev sa vezi ce posibilitati ai? > > > > > > > > Hello BSD-lovers, > > > > i'm stuck on a tricky situation: > > > > > > > > i got FreeBSD 4.8-STABLE running smoothly on a SCSI disk, > > > > but i had to move the HDD on a multi-OS system, so i am > > > > heading this problem: > > > > > > > > there are 3 disks > > > > - ad0: IDE WDC-drive with a MSwinOS > > > > - da0: SCSI IBM-drive with Debian Linux > > > > - da1: SCSI IBM FreeBSD disk > > > > > > > > ad0 is the primary disk with lilo in the MBR > > > > > > > > lilo.conf uses > > > > > > > > boot=/dev/hda > > > > ... > > > > /dev/sda1 to boot the debianOS > > > > /dev/sdb1 to boot FreeBSD > > > > > > > > well, this is working fine for winOS and linux but FreeBSD > > > > returns this error lines: > > > > > > > > Root mount failed: 22 > > > > Mounting root from ufs:/dev/da2s1a > > > > Root mount failed: 22 > > > > Mounting root from ufs:/dev/da2a > > > > Root mount failed: 22 > > > > > > > > Manual root filesystem specification: > > > > mountroot> > > > > > > > > > > > > i've tried all kind of combos like ufs:/dev/da1s1a but nothing worked out. > > > > what i still can't understand is why it's trying to mount /dev/da2 instead of > > > > /dev/da1 > > > > > > __ > > Send 'unsubscribe rofug' to [EMAIL PROTECTED] to unsubscribe > -- > Camelia Nastase > Network Administrator Motto: "All you have to do > Departamentul Internet is want it bad enough" > ASTRAL TELECOM SA, Sucursala Cluj > > > __ > Send 'unsubscribe rofug' to [EMAIL PROTECTED] to unsubscribe > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FYI: FreeBSD 5.0 under VMWare 2.0.4
Hi, Whoever tried FreeBSD 5.0-RELEASE/-current as a guest OS in VMWare (either 2.0.4 under FreeBSD 4.x or VMWare 3.2 under Windows NT platform) knows that it would run very slowly and even the system clock would run very quickly. One solution for this problem is to recompile your kernel with the following option: options CPU_DISABLE_CMPXCHG This works at least for VMWare 2.0.4 under FreeBSD 4. The options is documented in NOTES, in FreeBSD 5.x. Regards, Adrian Penisoara Ady (@freebsd.ady.ro) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Backspace and Delete keys under PuTTY
Hi,
On Tue, 10 Dec 2002, Ryan Thompson wrote:
> Jonathan Chen wrote to Adrian Penisoara:
>
> > On Tue, Dec 10, 2002 at 01:17:17PM +0200, Adrian Penisoara wrote:
> >
> > [...]
> >
> > > But I have Bash as the default shell. And yes, it works changing
> > > the Terminal / Keyboard / "Backspace key" from "Contrl-? (127)" to
> > > "Control-H", but the users are pissed off by the fact that Linux
> > > doesn't need this -- does it mean FreeBSD has broken termcap
> > > entries or that Linux is just stepping on the traditional
> > > standards ?
> >
> > It's Linux that's stepping on standards. Their default config is to
> > have erase=DEL. All other UNIX boxen I've used have erase=BACKASPCE.
> > I suspect the PUTTY writers have been heavily influenced by Linux.
>
Here's the explanation from the PuTTY's web documentation page[1]:
-
4.4.1 Changing the action of the Backspace key
Some terminals believe that the Backspace key should send the same thing
to the server as Control-H (ASCII code 8). Other terminals believe that
the Backspace key should send ASCII code 127 (usually known as
Control-?) so that it can be distinguished from Control-H. This option
allows you to choose which code PuTTY generates when you press
Backspace.
If you are connecting to a Unix system, you will probably find that the
Unix stty command lets you configure which the server expects to see, so
you might not need to change which one PuTTY generates. On other
systems, the server's expectation might be fixed and you might have no
choice but to configure PuTTY.
If you do have the choice, we recommend configuring PuTTY to generate
Control-? and configuring the server to expect it, because that allows
applications such as emacs to use Control-H for help.
--
Should all people go for this ?
> Has anyone taken the time to really fine tune PuTTY's settings to work
> well with FreeBSD and {n}curses apps? Somewhat ironically, the best
> results I have received thus far are to use xterm-color and ^H for
> erase. This works perfectly in tcsh/bash, but suffers somewhat in
> curses or ncurses programs such as PINE or lpe. Results with these
> settings vary depending on the application. PINE, for example, screams
> "Unknown Command" when I try to use Home/End/Delete/ PgUp/PgDn. With
> lpe, everything works except Home/End. Let me tell you, on a Dvorak
> keyboard, the usual ^Q and ^R aren't exactly intuitive or convenient.
> :-)
Once again, let's see PuTTY's sideview on their site[1]:
-
4.4.2 Changing the action of the Home and End keys
The Unix terminal emulator rxvt disagrees with the rest of the world
about what character sequences should be sent to the server by the Home
and End keys.
xterm, and other terminals, send ESC [1~ for the Home key, and ESC [4~
for the End key. rxvt sends ESC [H for the Home key and ESC [Ow for the
End key.
If you find an application on which the Home and End keys aren't
working, you could try switching this option to see if it helps.
On which side are we on ?
And for this matter let's see how the F? keys are standing on:
4.4.3 Changing the action of the function keys and keypad
This option affects the function keys (F1 to F12) and the top row of the
numeric keypad.
In the default mode, labelled ESC [n~, the function keys generate
sequences like ESC [11~, ESC [12~ and so on. This matches the general
behaviour of Digital's terminals.
In Linux mode, F6 to F12 behave just like the default mode, but F1 to F5
generate ESC [[A through to ESC [[E. This mimics the Linux virtual
console.
In Xterm R6 mode, F5 to F12 behave like the default mode, but F1 to F4
generate ESC OP through to ESC OS, which are the sequences produced by
the top row of the keypad on Digital's terminals.
In VT400 mode, all the function keys behave like the default mode, but
the actual top row of the numeric keypad generates ESC OP through to ESC
OS.
In VT100+ mode, the function keys generate ESC OP through to ESC O[
In SCO mode, the function keys F1 to F12 generate ESC [M through to ESC
[X. Together with shift, they generate ESC [Y through to ESC [j. With
control they generate ESC [k through to ESC [v, and with shift and
control together they generate ESC [w through to ESC [{.
If you don't know what any of this means, you probably don't need to
fiddle with it.
I
Re: Backspace and Delete keys under PuTTY
Hi, On Tue, 10 Dec 2002, Marcel Stangenberger wrote: > On Tue, 10 Dec 2002, Adrian Penisoara wrote: > > > What is the proper solution ? I'd rather prefer to modify the termcaps > > than making adjustments in PuTTY, as some persons get cranky when it > > comes about changing PuTTY settings while Linux works well with the > > defaults. > > > > proper way is to alter the putty settings for your connection to freebsd > machines. Another way is changing the default shell to bash. But I have Bash as the default shell. And yes, it works changing the Terminal / Keyboard / "Backspace key" from "Contrl-? (127)" to "Control-H", but the users are pissed off by the fact that Linux doesn't need this -- does it mean FreeBSD has broken termcap entries or that Linux is just stepping on the traditional standards ? Ady (@freebsd.ady.ro) | An age is called Dark not because the light fails to shine, but | | because people refuse to see it. | | -- James Michener, "Space" | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Backspace and Delete keys under PuTTY
Hi, I'm getting pissed (me and some other professors) by the Backspace and Delete keystrokes that are incorrectly handled by either PuTTY or FreeBSD when connecting to a FreeBSD system from a Windows workstation with PuTTY. No need to mention that when it comes to Linux everything looks fine. What is the proper solution ? I'd rather prefer to modify the termcaps than making adjustments in PuTTY, as some persons get cranky when it comes about changing PuTTY settings while Linux works well with the defaults. Thanks, Ady (@freebsd.ady.ro) | An age is called Dark not because the light fails to shine, but | | because people refuse to see it. | | -- James Michener, "Space" | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
