Impossible D

[Hoegard]

d’ailleurs au passage si tu connais un site ou une sorte de wiki qui explique les différentes commande possible en ssh je suis preneur

histoire de bien comprendre les manips que l'on a pu faire

et franchement suis super content, ravis, heureux !!!!!!!

je commençais à voir le formatage arriver ....

[Mr Akhlan]

Bonjour,

je me permet car j'ai exactement le même soucis et comme Hoegard, c'est apparu sur mon 7ème disque et aussi un WD...

Mais avant de me lancer, j'ai besoin d'une confirmation car pas envie de perdre mes 6 x 3To de données ^^....

MyNAS> tail -f /var/log/messages
Jul  3 16:19:20 MyNAS volumehandler.cgi: space_expand_unallocated.c:82 [Info] Success Dump map file
Jul  3 16:19:25 MyNAS kernel: [ 7787.577429] EXT4-fs warning (device dm-0): ext4_resize_fs:1997: No reserved GDT blocks, can't resize
Jul  3 16:19:25 MyNAS volumehandler.cgi: (fs_vol_expand.c)ExtFSExpand(88):Failed to '/sbin/resize2fs -fpF /dev/vg1000/lv > /dev/null 2>&1', WEXITSTATUS(r) = 1
Jul  3 16:19:25 MyNAS volumehandler.cgi: volume_manage_with_temp_dev.c:279 Failed to expand file system on /dev/vg1000/lv
Jul  3 16:19:25 MyNAS volumehandler.cgi: volume_lib.cpp:952 Failed to expand file system on /dev/vg1000/lv
Jul  3 16:19:25 MyNAS volumehandler.cgi: volumehandler.cpp:1444 failed to expand unallocated file system: /volume1

> df -h
Filesystem                Size      Used Available Use% Mounted on
/dev/md0                  2.3G    740.4M      1.5G  32% /
/tmp                      3.6G    700.0K      3.6G   0% /tmp
/dev/vg1000/lv           13.5T     13.1T    458.4G  97% /volume1

> pwd
/usr/syno/etc/rc.d
> ls -ltr | grep -i pgsql
>

> ps | grep -i postgres
 3628 root      3816 S    grep -i postgres
18537 postgres 38564 S    /usr/bin/postgres -D /var/services/pgsql
18962 postgres 38564 S    postgres: checkpointer process
18963 postgres 38564 S    postgres: writer process
18964 postgres 38564 S    postgres: wal writer process

donc pour moi ça serait ces commandes ?

killall postgres
./lsof /volume1 <----------------- lsof n'est pas installé sur mon NAS
umount /volume1
fsck.ext4 -y /dev/vg1000/lv
mount /dev/vg1000/lv /volume1

reboot

J'ai arrêté toutes mes applis, pas d'indexation,...

Je ne risque rien en faisant cela ?

Merci

Akhlan

[Fravadona]

/var/log/messages ne parle pas de corruption dans le système de fichiers ext4 , je ne suis pas sur qu'un fsck puisse resoudre le souci

Sinon pour la procedure ca m'a l'air correct, et tu ne risques "quasiment rien" avec un fsck mis a part perdre quelques fichiers qui seraient réellement corrompus.

[Mr Akhlan]

donc ça risque de ne même pas résoudre mon problème alors ?

Pourtant nos erreurs semblent assez similaire...

Hoegard :
kernel: [66650.572404] EXT4-fs warning (device dm-7): ext4_resize_begin:32: There are errors in the filesystem, so online resizing is not allowed
volumehandler.cgi: (fs_vol_expand.c)ExtFSExpand(88):Failed to '/sbin/resize2fs -fpF /dev/mapper/vol1-origin > /dev/null 2>&1', WEXITSTATUS® = 1
volumehandler.cgi: volume_manage_with_temp_dev.c:279 Failed to expand file system on /dev/mapper/vol1-origin
volumehandler.cgi: volume_lib.cpp:1017 Failed to expand file system on /dev/mapper/vol1-origin
volumehandler.cgi: volumehandler.cpp:1444 failed to expand unallocated file system: /volume1

Moi :
volumehandler.cgi: space_expand_unallocated.c:82 [info] Success Dump map file
kernel: [ 7787.577429] EXT4-fs warning (device dm-0): ext4_resize_fs:1997: No reserved GDT blocks, can't resize
volumehandler.cgi: (fs_vol_expand.c)ExtFSExpand(88):Failed to '/sbin/resize2fs -fpF /dev/vg1000/lv > /dev/null 2>&1', WEXITSTATUS® = 1
volumehandler.cgi: volume_manage_with_temp_dev.c:279 Failed to expand file system on /dev/vg1000/lv
volumehandler.cgi: volume_lib.cpp:952 Failed to expand file system on /dev/vg1000/lv
volumehandler.cgi: volumehandler.cpp:1444 failed to expand unallocated file system: /volume1

Alors....
monNAS> umount /volume1
monNAS>
monNAS> fsck.ext4 -y /dev/vg1000/lv
e2fsck 1.42.6 (21-Sep-2012)
1.42.6-3211: is cleanly umounted, 937079/457117696 files, 3536712620/3656913920 blocks
monNAS>
monNAS> mount /dev/vg1000/lv /volume1
monNAS>
monNAS> reboot

Verdict.................
Snifffff, toujours pareil, impossible d'ajouter mon 7ème disque :-(

"Vous pouvez faire passer le volume à environ 16740Go." et quand je clic sur "Gérer" / "Étendre le volume avec l'espace....", ça travaille pendant 30 secondes et ça me remet le même message... "Vous pouvez faire passer le volume à environ 16740Go."

monNAS> tail -f /var/log/messages
Jul  3 19:23:29 monNAS storagehandler.cgi: volume_fs_cache_enum.c:42 failed to alloc list. [0x0900 file_enum_section.c:46]
Jul  3 19:23:29 monNAS storagehandler.cgi: volume_fs_cache_enum.c:42 failed to alloc list. [0x0900 file_enum_section.c:46]
Jul  3 19:23:41 monNAS storagehandler.cgi: volume_fs_cache_enum.c:42 failed to alloc list. [0x0900 file_enum_section.c:46]
Jul  3 19:23:41 monNAS storagehandler.cgi: volume_fs_cache_enum.c:42 failed to alloc list. [0x0900 file_enum_section.c:46]
Jul  3 19:23:51 monNAS storagehandler.cgi: volume_fs_cache_enum.c:42 failed to alloc list. [0x0900 file_enum_section.c:46]
Jul  3 19:23:51 monNAS storagehandler.cgi: volume_fs_cache_enum.c:42 failed to alloc list. [0x0900 file_enum_section.c:46]
Jul  3 19:24:02 monNAS storagehandler.cgi: volume_fs_cache_enum.c:42 failed to alloc list. [0x0900 file_enum_section.c:46]
Jul  3 19:24:02 monNAS storagehandler.cgi: volume_fs_cache_enum.c:42 failed to alloc list. [0x0900 file_enum_section.c:46]
Jul  3 19:24:36 monNAS S99zbootok.sh: Error! synoservices start failed! (service [ntpd-server] is not ready, please wait...)
Jul  3 19:24:44 monNAS ntpdate: Sync with time server 212.85.158.10 offset -0.083590 sec.
Jul  3 19:25:59 monNAS volumehandler.cgi: space_expand_unallocated.c:82 [Info] Success Dump map file
Jul  3 19:26:04 monNAS kernel: [  295.826690] EXT4-fs warning (device dm-0): ext4_resize_fs:1997: No reserved GDT blocks, can't resize
Jul  3 19:26:04 monNAS volumehandler.cgi: (fs_vol_expand.c)ExtFSExpand(88):Failed to '/sbin/resize2fs -fpF /dev/vg1000/lv > /dev/null 2>&1', WEXITSTATUS(r) = 1
Jul  3 19:26:04 monNAS volumehandler.cgi: volume_manage_with_temp_dev.c:279 Failed to expand file system on /dev/vg1000/lv
Jul  3 19:26:04 monNAS volumehandler.cgi: volume_lib.cpp:952 Failed to expand file system on /dev/vg1000/lv
Jul  3 19:26:04 monNAS volumehandler.cgi: volumehandler.cpp:1444 failed to expand unallocated file system: /volume1

Modifié le 3 juillet 2014 par akhlan

[Fravadona]

Tu as peut-etre une limitation de 16To, verifies la fiche technique de ton NAS.

Ce qui te bloque toi est :

kernel: [ 295.826690] EXT4-fs warning (device dm-0): ext4_resize_fs:1997: No reserved GDT blocks, can't resize

Alors que le probleme precedent qui necessitait un fsck etait :

kernel: [66650.572404] EXT4-fs warning (device dm-7): ext4_resize_begin:32: There are errors in the filesystem, so online resizing is not allowed

Modifié le 3 juillet 2014 par Fravadona

[Fravadona]

> I have an ext4 partition that seems to have used all reserved gdt blocks.

The original on-line resize scheme required gdt blocks to be reserved so there would be room for the group descriptor table blocks (which had to be contiguous). The number of group descriptor blocks that was reserved calculated to be a thousand times the size of the original file system, which would normally be enough. *But* it was also capped by a limitation in how we reserved the gdt blocks such that the sum of the in-use gdt blocks plus reserved gdt blocks could not exceed 1024 blocks. Before the 64-bit option, this was not a problem, since we would hit the 16T limitation at the same time. However, when the 64-bit option is enabled, it's possible to run out of gdt blocks using the old scheme; this is the limitation which you hit.

We have added a new on-line resizing scheme in the 3.7 kernel, which does not require that block group descriptors be contiguous. However, it requires also the 1.42.6 version of e2fsprogs

Pour ce qui est de e2fsprogs le Syno (DSM 4.3) semble posseder la bonne version, mais vu que ca bloque tout de meme pour cause de GDT non alloués cela veut dire que c'est le kernel (3.2) du Syno qui est fautif.

La seule solution pour toi serait de casser ton volume puis de le recreer directement avec tous les disques.

[Mr Akhlan]

casser = perdre toutes les données ?

[Fravadona]

Malheusement oui.

Tu peux peut-etre contacter Syno, ils pourraient avoir une solution comme te fournir un kernel Linux specialement pour pouvoir faire ca

[Mr Akhlan]

J'ai trouvé une solution sur un autre forum, je post ici aussi si besoin

DiskStation> cat /var/log/messages

Aug 9 22:59:36 DiskStation volumehandler.cgi: space_expand_unallocated.c:82 [info] Success Dump map file

Aug 9 22:59:41 DiskStation kernel: [112761.381625] EXT4-fs warning (device dm-0): ext4_resize_fs:1996: No reserved GDT blocks, can't resize

Aug 9 22:59:41 DiskStation volumehandler.cgi: (fs_vol_expand.c)ExtFSExpand(88):Failed to '/sbin/resize2fs -fpF /dev/vg1000/lv > /dev/null 2>&1', WEXITSTATUS® = 1

Aug 9 22:59:41 DiskStation volumehandler.cgi: volume_manage_with_temp_dev.c:279 Failed to expand file system on /dev/vg1000/lv

Aug 9 22:59:41 DiskStation volumehandler.cgi: volume_lib.cpp:952 Failed to expand file system on /dev/vg1000/lv

Aug 9 22:59:41 DiskStation volumehandler.cgi: volumehandler.cpp:1444 failed to expand unallocated file system: /volume1

DiskStation> cat /etc/fstab

none /proc proc defaults 0 0

/dev/root / ext4 defaults 1 1

/dev/vg1000/lv /volume1 ext4 usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,synoacl 0 0

DiskStation> pwd

/usr/syno/etc/rc.d

DiskStation> killall postgres

DiskStation> umount -f /volume1

DiskStation> fsck.ext4 -fvp /dev/vg1000/lv

948887 inodes used (0.21%, out of 457117696)

7689 non-contiguous files (0.8%)

292 non-contiguous directories (0.0%)

# of inodes with ind/dind/tind blocks: 0/0/0

Extent depth histogram: 938097/6591

3596495474 blocks used (98.35%, out of 3656913920)

0 bad blocks

1766 large files

716505 regular files

188593 directories

12 character device files

25 block device files

2 fifos

30 links

43740 symbolic links (4151 fast symbolic links)

1 socket

------------

948908 files

DiskStation> /sbin/resize2fs -fpF /dev/vg1000/lv

resize2fs 1.42.6 (21-Sep-2012)

Resizing the filesystem on /dev/vg1000/lv to 4388296704 (4k) blocks.

Begin pass 2 (max = 689)

Relocating blocks XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Begin pass 3 (max = 111601)

Scanning inode table XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Begin pass 5 (max = 1)

Moving inode table XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

The filesystem on /dev/vg1000/lv is now 4388296704 blocks long.

DiskStation> reboot

Broadcast message from root@DiskStation

(/dev/pts/1) at 0:27 ...

The system is going down for reboot NOW!

DiskStation> Connection to 192.xxx.xxx.xxx closed by remote host.

Connection to 192.xxx.xxx.xxx closed.

et me voilà avec mes 16To ^^