[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: copie de dossiers par rsync mais taille differente au final

Bonjour
 
Le 22/03/06, Jacques L'helgoualc'h <lhh+no_spam@free.fr > a écrit :
Matthieu a écrit, mercredi 22 mars 2006, à 07:59 :
> bonjour

bonjour,

Heu, l'unité doit être le kilo-octet, a priori (sauf POSIXLY_CORRECT, où
c'est 512 octets). M'enfin, j'ai ça avec un /lost+found/ *vide* :
 
oui mes lost+found sont vides.

 
Si tes */lost+found/ sont vides, je pense à une différence de taille des
blocs  d'allocation ---  à  vérifier  par «tune2fs  -l»  sur les  deux
/dev/hd? concernées.
 
La ca commence a devenir pointu :) je t'avouerais que je suis un peu perdu par rapport aux resultats retournés par
 
tune2fs -l /dev/hdb1

tune2fs 1.37 (21-Mar-2005)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          41f2bd90-14f8-4588-b75f-5294d0a5c0f5
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal filetype needs_recovery sparse_super
Default mount options:    (none)
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              61063168
Block count:              122096000
Reserved block count:     6104800
Free blocks:              34428672
Free inodes:              61062657
First block:              0
Block size:               4096
Fragment size:            4096
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         16384
Inode blocks per group:   512
Filesystem created:       Mon Jan 30 22:09:57 2006
Last mount time:          Wed Mar 22 08:58:26 2006
Last write time:          Wed Mar 22 08:58:26 2006
Mount count:              6
Maximum mount count:      31
Last checked:             Mon Jan 30 22:09:57 2006
Check interval:           15552000 (6 months)
Next check after:         Sat Jul 29 23:09:57 2006
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               128
Journal inode:            8
Default directory hash:   tea
Directory Hash Seed:      6a092fbc-c14d-49e9-a577-f3bbc5d0777b
Journal backup:           inode blocks
 
tune2fs -l /dev/hdc1
 
tune2fs 1.37 (21-Mar-2005)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          e72f26c6-3dc5-40d5-a3a5-cfd5213d9a40
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal filetype needs_recovery sparse_super
Default mount options:    (none)
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              61063168
Block count:              122096000
Reserved block count:     6104800
Free blocks:              34428670
Free inodes:              61062655
First block:              0
Block size:               4096
Fragment size:            4096
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         16384
Inode blocks per group:   512
Filesystem created:       Tue Jan 31 00:18:45 2006
Last mount time:          Wed Mar 22 08:58:26 2006
Last write time:          Wed Mar 22 08:58:26 2006
Mount count:              5
Maximum mount count:      29
Last checked:             Tue Jan 31 00:18:45 2006
Check interval:           15552000 (6 months)
Next check after:         Sun Jul 30 01:18:45 2006
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               128
Journal inode:            8
Default directory hash:   tea
Directory Hash Seed:      8d340ade-ecca-4403-94f2-dfb7c0645943
Journal backup:           inode blocks
 
diff /root/b1.txt /root/c1.txt
4c4
< Filesystem UUID:          41f2bd90-14f8-4588-b75f-5294d0a5c0f5
---
> Filesystem UUID:          e72f26c6-3dc5-40d5-a3a5-cfd5213d9a40
15,16c15,16
< Free blocks:              34428672
< Free inodes:              61062657
---
> Free blocks:              34428670
> Free inodes:              61062655
24c24
< Filesystem created:       Mon Jan 30 22:09:57 2006
---
> Filesystem created:       Tue Jan 31 00:18:45 2006
27,29c27,29
< Mount count:              6
< Maximum mount count:      31
< Last checked:             Mon Jan 30 22:09:57 2006
---
> Mount count:              5
> Maximum mount count:      29
> Last checked:             Tue Jan 31 00:18:45 2006
31c31
< Next check after:         Sat Jul 29 23:09:57 2006
---
> Next check after:         Sun Jul 30 01:18:45 2006
38c38
< Directory Hash Seed:      6a092fbc-c14d-49e9-a577-f3bbc5d0777b
---
> Directory Hash Seed:      8d340ade-ecca-4403-94f2-dfb7c0645943
 
df
 
/dev/hdb1            480719056 343004368 113295488  76% /var/www
/dev/hdc1            480719056 343004376 113295480  76% /bkp/www
 
et voici les informations que j'ai eu lors de mon dernier reboot dans /var/log/messages concernant les disques dont je vous parle...
 
...
Mar 22 07:58:44 localhost kernel: hdb: HDS725050KLAT80, ATA DISK drive
Mar 22 07:58:44 localhost kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Mar 22 07:58:44 localhost kernel: hdc: HDS725050KLAT80, ATA DISK drive
Mar 22 07:58:44 localhost kernel: ide1 at 0x170-0x177,0x376 on irq 15
Mar 22 07:58:44 localhost kernel: hdb: max request size: 1024KiB
Mar 22 07:58:44 localhost kernel: hdb: Host Protected Area detected.
Mar 22 07:58:44 localhost kernel: ^Icurrent capacity is 976771055 sectors (500106 MB)
Mar 22 07:58:44 localhost kernel: ^Inative  capacity is 976773168 sectors (500107 MB)
Mar 22 07:58:44 localhost kernel: hdb: 976771055 sectors (500106 MB) w/7663KiB Cache, CHS=60801/255/63, UDMA(133)
Mar 22 07:58:44 localhost kernel:  /dev/ide/host0/bus0/target1/lun0: p1
Mar 22 07:58:44 localhost kernel: hdc: max request size: 1024KiB
Mar 22 07:58:44 localhost kernel: hdc: 976773168 sectors (500107 MB) w/7663KiB Cache, CHS=60801/255/63, UDMA(33)
Mar 22 07:58:44 localhost kernel:  /dev/ide/host0/bus1/target0/lun0: p1
...
Mar 22 07:58:44 localhost kernel: EXT3 FS on hdb1, internal journal
Mar 22 07:58:44 localhost kernel: EXT3-fs: mounted filesystem with ordered data mode.
Mar 22 07:58:44 localhost kernel: kjournald starting.  Commit interval 5 seconds
Mar 22 07:58:44 localhost kernel: EXT3 FS on hdc1, internal journal
Mar 22 07:58:44 localhost kernel: EXT3-fs: mounted filesystem with ordered data mode.
 
 
la je suis un peu perplexe
Pourquoi les disques ne font pas la meme taille alors que ce sont exactement les memes modeles? Est ce que la difference d'UDMA - qui soit dit en passant me laisse aussi perplexe - peut etre a l'origine du probleme. J'imagines que non, mais n'ayant pas la science infuse... :)
 
je vous joins aussi mes logs smartd concernant ces deux disques, peut etre que cela peut vous aider a comprendre, moi ca me laisse perplexe :)
 
Mar 19 10:10:27 localhost smartd[7941]: Device: /dev/hdc, SMART Prefailure Attribute: 8 Seek_Time_Performance changed from 134 to 100
Mar 19 10:40:26 localhost smartd[7941]: Device: /dev/hdb, SMART Prefailure Attribute: 8 Seek_Time_Performance changed from 134 to 136
Mar 19 10:40:27 localhost smartd[7941]: Device: /dev/hdc, SMART Prefailure Attribute: 8 Seek_Time_Performance changed from 100 to 132
Mar 19 14:10:27 localhost smartd[7941]: Device: /dev/hdc, SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 100 to 99
Mar 19 14:40:27 localhost smartd[7941]: Device: /dev/hdc, SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 99 to 100
Mar 19 15:10:27 localhost smartd[7941]: Device: /dev/hdc, SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 100 to 99
Mar 19 15:40:27 localhost smartd[7941]: Device: /dev/hdc, SMART Prefailure Attribute: 1 Raw_Read_Error_Rate changed from 99 to 100
Mar 20 02:10:29 localhost smartd[7941]: Device: /dev/hdb, starting scheduled Short Self-Test.
Mar 20 02:10:33 localhost smartd[7941]: Device: /dev/hdc, starting scheduled Short Self-Test.
Mar 20 15:40:26 localhost smartd[7941]: Device: /dev/hdb, SMART Prefailure Attribute: 8 Seek_Time_Performance changed from 136 to 134
Mar 20 16:10:27 localhost smartd[7941]: Device: /dev/hdc, SMART Prefailure Attribute: 8 Seek_Time_Performance changed from 132 to 136
Mar 21 02:10:30 localhost smartd[7941]: Device: /dev/hdb, starting scheduled Short Self-Test.
Mar 21 02:10:33 localhost smartd[7941]: Device: /dev/hdc, starting scheduled Short Self-Test.
Mar 21 21:40:27 localhost smartd[7941]: Device: /dev/hdb, SMART Prefailure Attribute: 8 Seek_Time_Performance changed from 134 to 136
Mar 22 02:10:29 localhost smartd[7941]: Device: /dev/hdb, starting scheduled Short Self-Test.
Mar 22 02:10:32 localhost smartd[7941]: Device: /dev/hdc, starting scheduled Short Self-Test.
Mar 22 07:57:19 localhost smartd[7941]: smartd received signal 15: Terminated
Mar 22 07:57:19 localhost smartd[7941]: smartd is exiting (exit status 0)
Mar 22 07:58:48 localhost smartd[2155]: smartd version 5.32 Copyright (C) 2002-4 Bruce Allen
Mar 22 07:58:48 localhost smartd[2155]: Home page is http://smartmontools.sourceforge.net/
Mar 22 07:58:48 localhost smartd[2155]: Opened configuration file /etc/smartd.conf
Mar 22 07:58:48 localhost smartd[2155]: Configuration file /etc/smartd.conf parsed.
Mar 22 07:58:48 localhost smartd[2155]: Device: /dev/hdb, opened
Mar 22 07:58:48 localhost smartd[2155]: Device: /dev/hdb, not found in smartd database.
Mar 22 07:58:49 localhost smartd[2155]: Device: /dev/hdb, is SMART capable. Adding to "monitor" list.
Mar 22 07:58:49 localhost smartd[2155]: Device: /dev/hdc, opened
Mar 22 07:58:49 localhost smartd[2155]: Device: /dev/hdc, not found in smartd database.
Mar 22 07:58:50 localhost smartd[2155]: Device: /dev/hdc, is SMART capable. Adding to "monitor" list.
Mar 22 07:58:50 localhost smartd[2155]: Monitoring 2 ATA and 0 SCSI devices
..
Mar 22 10:28:52 localhost smartd[2158]: Device: /dev/hdc, SMART Prefailure Attribute: 8 Seek_Time_Performance changed from 136 to 134
Mar 23 02:28:55 localhost smartd[2158]: Device: /dev/hdb, starting scheduled Short Self-Test.
Mar 23 02:28:58 localhost smartd[2158]: Device: /dev/hdc, starting scheduled Short Self-Test.
 
Matthieu

--
Jacques L'helgoualc'h


--
Pensez à lire la FAQ de la liste avant de poser une question :
http://wiki.debian.net/?DebianFrench

Pensez à rajouter le mot ``spam'' dans vos champs "From" et "Reply-To:"

To UNSUBSCRIBE, email to debian-user-french-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org


Reply to: