Le 23/10/2012 14:47, Les Mikesell a écrit :
On Tue, Oct 23, 2012 at 3:23 AM, Frédéric Massot
frede...@juliana-multimedia.com wrote:
Just curious: does the content you back up consist mostly of tiny
files without much duplication? It seems odd to run out of inodes
while still having
Le 15/10/2012 17:05, Les Mikesell a écrit :
On Mon, Oct 15, 2012 at 9:40 AM, Frédéric Massot
frede...@juliana-multimedia.com wrote:
The problem is that the original file system (ext4) has no inode
available and increasing the size of an ext4 file system does not
increase the number of the
On Tue, Oct 23, 2012 at 3:23 AM, Frédéric Massot
frede...@juliana-multimedia.com wrote:
Just curious: does the content you back up consist mostly of tiny
files without much duplication? It seems odd to run out of inodes
while still having substantial disk space.
I used the command df -i
On 10/14 06:30 , Frederic MASSOT wrote:
I started copying Backuppc data from /var/lib/backuppc (ext4) to the
temporary directory /mnt/backuppc-new (xfs) with the command cp -a.
Due to the hardlinks, the only way to copy the backuppc data pool from one
set of disks to another at anything like
Le 15/10/2012 15:32, Carl Wilhelm Soderstrom a écrit :
On 10/14 06:30 , Frederic MASSOT wrote:
I started copying Backuppc data from /var/lib/backuppc (ext4) to the
temporary directory /mnt/backuppc-new (xfs) with the command cp -a.
Due to the hardlinks, the only way to copy the backuppc data
On Mon, Oct 15, 2012 at 8:32 AM, Carl Wilhelm Soderstrom
chr...@real-time.com wrote:
On 10/14 06:30 , Frederic MASSOT wrote:
I started copying Backuppc data from /var/lib/backuppc (ext4) to the
temporary directory /mnt/backuppc-new (xfs) with the command cp -a.
Due to the hardlinks, the only
On 10/15 04:40 , Frédéric Massot wrote:
The problem is that the original file system (ext4) has no inode
available and increasing the size of an ext4 file system does not
increase the number of the inode. To have no more inode problem the new
filesystem is xfs, so I can not copy data with
On Mon, Oct 15, 2012 at 9:40 AM, Frédéric Massot
frede...@juliana-multimedia.com wrote:
The problem is that the original file system (ext4) has no inode
available and increasing the size of an ext4 file system does not
increase the number of the inode. To have no more inode problem the new
Le 14/10/2012 18:01, Frederic MASSOT a écrit :
Le 08/10/2012 13:47, Carl Wilhelm Soderstrom a écrit :
On 10/08 11:07 , Frédéric Massot wrote:
After moving the BackupPC data on the new logical volume and thus the
new file system, the old logical volume will no longer be used. I could
On Sun, Oct 14, 2012 at 11:30 AM, Frederic MASSOT
frede...@juliana-multimedia.com wrote:
But now it is very slow, the speed is closer to 1 GB in 12 hours, or
more. It remains to be copied 200 GB, I can not wait 100 days!
Copy of cpool and log was performed, the slowness comes from the
copy
Le 07/10/2012 23:56, Michael Stowe a écrit :
The file system has the option resize_inode is that it can help to
increase the size or number of inode?
resize_inode is a flag you can set when you first create the filesystem,
that makes it easier to expand the file system later. Again, when
On 10/08 11:07 , Frédéric Massot wrote:
After moving the BackupPC data on the new logical volume and thus the
new file system, the old logical volume will no longer be used. I could
delete it but how I could use this free space?
Expand your new volume and filesystem to use it.
Are you using
Le 08/10/2012 13:47, Carl Wilhelm Soderstrom a écrit :
On 10/08 11:07 , Frédéric Massot wrote:
After moving the BackupPC data on the new logical volume and thus the
new file system, the old logical volume will no longer be used. I could
delete it but how I could use this free space?
Expand
On 10/08 03:01 , Frédéric Massot wrote:
I thought I would increase the size of the new file system, but my
concern is not having the same problem with a lack of inode in a few years.
From what I've read, if I chose XFS instead of ext4, I would not have
this problem of lack of inode.
Le 04/10/2012 20:56, Michael Stowe a écrit :
The inode number of the ext4 is static.
- How can I do to increase the number of inodes?
The number of ext4 inodes are set when the ext4 volume is created, so, you
have to recreate the file system. Perhaps using an alternative to ext4.
I
The file system has the option resize_inode is that it can help to
increase the size or number of inode?
resize_inode is a flag you can set when you first create the filesystem,
that makes it easier to expand the file system later. Again, when you
first create... so ... no.
So I must create
On 2012-10-04 19:56, Michael Stowe wrote:
The inode number of the ext4 is static.
- How can I do to increase the number of inodes?
The number of ext4 inodes are set when the ext4 volume is created, so, you
have to recreate the file system. Perhaps using an alternative to ext4.
I wonder
On Fri, Oct 5, 2012 at 3:58 AM, Tyler J. Wagner ty...@tolaris.com wrote:
On 2012-10-04 19:56, Michael Stowe wrote:
The inode number of the ext4 is static.
- How can I do to increase the number of inodes?
The number of ext4 inodes are set when the ext4 volume is created, so, you
have to
On Fri, Oct 5, 2012 at 6:42 AM, Les Mikesell lesmikes...@gmail.com wrote:
I wonder what caused this. My BackupPC filesystem was created with default
mkfs.ext4, and has used far more disk space than inodes:
Filesystem Size Used Avail Use% Mounted on
/dev/md03.6T 1.6T 2.1T
I can't math today, I have the dumb...
On Fri, Oct 5, 2012 at 9:24 AM, Ray Frush ray.fr...@avagotech.com wrote:
Out of curiosity, I checked some of our primary storage, where we
have a mix of lots (over 1Billion) of really small files and some
large databases, and found we're using about 7
Hi,
The night's backup has not worked, in logs there is an error message on
the hards links. I rebooted the server to do a fsck. It found no error,
but did not start backuppc.
In the log there : Can't create a test hardlink between a file in
/var/lib/backuppc/pc and /var/lib/backuppc/cpool.
The inode number of the ext4 is static.
- How can I do to increase the number of inodes?
The number of ext4 inodes are set when the ext4 volume is created, so, you
have to recreate the file system. Perhaps using an alternative to ext4.
- I can replace one by one the 500GB drives with 1TB
22 matches
Mail list logo
