13.01.2012 17:22, Stuart Henderson P?P8QP5Q:
On 2012/01/13 16:55, lilit-aibolit wrote:
13.01.2012 16:11, Stuart Henderson P?P8QP5Q:
a: 1.0G 63 4.2BSD 2048 163841 # /
b: 1.2G 2097215swap
c:37.3G
On Fri, Jan 13, 2012 at 04:20:07PM +0200, Vitali wrote:
> >> There is one more philosophical side effect of this question - speed.
> >> The closer the partition is placed to the outer cylinders, the faster
> >> the data are read from it.
> >
> > More a methaphysical question. On modern disks, the
On 01/13/2012 09:55 AM, lilit-aibolit wrote:
13.01.2012 16:11, Stuart Henderson P?P8QP5Q:
a: 1.0G 63 4.2BSD 2048 16384 1 # /
b: 1.2G 2097215 swap
c: 37.3G 0 unused
d: 2.6G 4683375 4.2BSD 2048 16384 1 # /tmp
e: 4.0G 10052439 4.2BSD 2048 16384 1 # /var
f: 2.0G 18541648 4.2BSD 2048 16384 1 # /us
On Fri, Jan 13, 2012 at 03:45:47PM +0200, lilit-aibolit wrote:
> 13.01.2012 14:28, Francois Pussault P?P8QP5Q:
>
> >
> >With a so huge /var 90% is anormal, you should already look for a
logrotate
> >solution or choose a new partition map you will use on next update of the
> >machine.
> >
That wa
On 2012/01/13 16:55, lilit-aibolit wrote:
> 13.01.2012 16:11, Stuart Henderson P?P8QP5Q:
>
> >a: 1.0G 63 4.2BSD 2048 163841 # /
> >b: 1.2G 2097215swap
> >c:37.3G0 unused
> >d: 2.6G
On Fri, 13 Jan 2012 16:55:04 +0200
lilit-aibolit wrote:
> 13.01.2012 16:11, Stuart Henderson P?P8QP5Q:
>
> > a: 1.0G 63 4.2BSD 2048 163841
> > # / b: 1.2G 2097215swap
> > c:37.3G0 unused
> > d:
On 2012-01-13 15.55, lilit-aibolit wrote:
> I got the same recommendation from Vadim Zhukov persg...@gmail.com
> with little difference, do it in single mode:
> 1. Boot in single user mode, enter shell.
> 2. mount /, /usr, /var and /home.
> 3. Move /var/* to /home.
> 4. Move /home/* to /var (except
13.01.2012 16:11, Stuart Henderson P?P8QP5Q:
a: 1.0G 63 4.2BSD 2048 163841 # /
b: 1.2G 2097215swap
c:37.3G0 unused
d: 2.6G 4683375 4.2BSD 2048 163841 # /tmp
e:
>> There is one more philosophical side effect of this question - speed.
>> The closer the partition is placed to the outer cylinders, the faster
>> the data are read from it.
>
> More a methaphysical question. On modern disks, the correspondence
> between block/cyl number and physcial location is
On 2012-01-13, lilit-aibolit wrote:
> 13.01.2012 14:28, Francois Pussault P?P8QP5Q:
>
>>
>> With a so huge /var 90% is anormal, you should already look for a logrotate
>> solution or choose a new partition map you will use on next update of the
>> machine.
>>
>
> First of all, thanks all for you
On Fri, Jan 13, 2012 at 03:20:20PM +0200, Vitali wrote:
> On Fri, Jan 13, 2012 at 2:28 PM, Francois Pussault
> wrote:
> > I prefer to define my parts manualy like this
> > A / 256Mo
> > enough free space on the fastest disk in the machine
> >
>
> [cut]
>
> > When your /var will be full, it will
[cut]
> 2.2G B B total
>
> do I understand correctly, that in my case the easiest way is
> decrease /home and increase /var?
>
Taking into account that your /home is used only by 2% (the least used
of the largest by size) and your /var is used by 90% and you need more
there, - then yes. :)
--
##
13.01.2012 14:28, Francois Pussault P?P8QP5Q:
With a so huge /var 90% is anormal, you should already look for a logrotate
solution or choose a new partition map you will use on next update of the
machine.
First of all, thanks all for your replies.
As I said /var is used for www-aplication
On Fri, Jan 13, 2012 at 2:28 PM, Francois Pussault
wrote:
> I prefer to define my parts manualy like this
> A / 256Mo
> enough free space on the fastest disk in the machine
>
[cut]
> When your /var will be full, it will not grow up, you have to purge some
log
> files (use logrotate or so will he
fpussa...@contactoffice.fr (Francois Pussault), 2012.01.13 (Fri) 13:28 (CET):
> J /home all of the free space
may I just throw in: fsck duration upon boot after unclean unmount.
A good philosophy: as little as possible (fsck duration), as much as
necessary (user/service reqirement).
Needed: ha
On Friday, January 13, 2012, Zi Loff wrote:
> Hi
>
> If I added it up correctly, you don't have any unused space on your disk.
> As stated on the FAQ (4.6.4)
>"c" on all disks is the "whole disk" partition, it is used by
programs that
> have to have raw access to the physical disk, such as
Hi
If I added it up correctly, you don't have any unused space on your disk.
As stated on the FAQ (4.6.4)
"c" on all disks is the "whole disk" partition, it is used by programs
that
have to have raw access to the physical disk, such as fdisk(8) and
disklabel(8).
So, although disklabel sa
ld already look for a logrotate
solution or choose a new partition map you will use on next update of the
machine.
>
> From: lilit-aibolit
> Sent: Fri Jan 13 12:40:37 CET 2012
> To:
> Subject: disk management
>
>
> Hi misc. Here is new
On Fri, 13 Jan 2012 14:12:46 +0200
Vitali wrote:
> On Fri, Jan 13, 2012 at 1:40 PM, lilit-aibolit
> wrote:
> > Hi misc. Here is newbee question.
> > I have disk with unused space:
> >
> > # disklabel -p g wd0
> > B k: B B B B B B 18.1G B B B B 40266255 B 4.2BSD B 2048
> > 16384 B
> B
On Fri, Jan 13, 2012 at 1:40 PM, lilit-aibolit wrote:
> Hi misc. Here is newbee question.
> I have disk with unused space:
>
> # disklabel -p g wd0
> B k: B B B B B B 18.1G B B B B 40266255 B 4.2BSD B 2048 16384 B
B 1 # /home
>
[some text is cut]
>
> In /var I store some sites for apach
Hi,
On Friday, 13 Jan 2012 at 13:40 CET
lilit-aibolit wrote:
> Hi misc. Here is newbee question.
> I have disk with unused space:
>
> # disklabel -p g wd0
> 16 partitions:
> # sizeoffset fstype [fsize bsize cpg]
> a: 1.0G63 4.2BSD 2048 163841 # /
>
Hi misc. Here is newbee question.
I have disk with unused space:
# disklabel -p g wd0
16 partitions:
#size offset fstype [fsize bsize cpg]
a: 1.0G 63 4.2BSD 2048 163841 # /
b: 1.2G 2097215swap
c:
22 matches
Mail list logo
