All disks are XFS, apart form parity, which is formated with "mkfs.ext4 -m 0 -T largefile4 DEVICE"
Now, when I try to run snapraid -v sync, every time (after deleting failed content and parity files) it ends the same:
# snapraid -v syncSelftest...Loadingstatefrom/mnt/storage_parts/samsung_2x0.5tb_new/SnapRAID.content...WARNING!Contentfile'/mnt/storage_parts/samsung_2x0.5tb_new/SnapRAID.content'notfound,tryingwithanothercopy...Loadingstatefrom/mnt/storage_parts/hitachi_1tb/SnapRAID.content...WARNING!Contentfile'/mnt/storage_parts/hitachi_1tb/SnapRAID.content'notfound,tryingwithanothercopy...Loadingstatefrom/mnt/storage_parts/samsung_320gb/SnapRAID.content...WARNING!Contentfile'/mnt/storage_parts/samsung_320gb/SnapRAID.content'notfound,tryingwithanothercopy...Loadingstatefrom/var/snapraid/SnapRAID.content...Nocontentfilefound.Assumingempty.Scanningdiskd1...Excludingcontent'/mnt/storage_parts/samsung_2x0.5tb_new/SnapRAID.content.lock'Scanningdiskd2...Scanningdiskd3...Scanningdiskd4...0equal474483added0removed0updated0moved0copied0restoredUsing385MiBofmemoryfortheFileSystem.Initializing...Savingstateto/mnt/storage_parts/samsung_2x0.5tb_new/SnapRAID.content...Savingstateto/mnt/storage_parts/hitachi_1tb/SnapRAID.content...Savingstateto/mnt/storage_parts/samsung_320gb/SnapRAID.content...Savingstateto/var/snapraid/SnapRAID.content...(...Icutabout200linesjustlikethosebelow...)outofparity/mnt/storage_parts/samsung_2x0.5tb_new/media/series/24/24Season4/24-[4x18]-12.00AM-01.00AM.mkvoutofparity/mnt/storage_parts/samsung_2x0.5tb_new/media/series/24/24Season4/24-[4x01]-07.00AM-08.00AM..mkvoutofparity/mnt/storage_parts/samsung_2x0.5tb_new/media/series/24/24Season4/24-[4x02]-08.00AM-09.00AM.mkvWARNING!WithoutanaccessibleParityfile,itisn't possible to sync.
I had this problem before, but after deleting one folder, it went through. However, limiting number of files is not possible anymore.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The issue is that the data disks are too filled, and there isn't space in the parity for all the files marked as "outofparity". If you move them to another data disk, you should be able to sync.
Ciao,
Andrea
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Do you mean the small 320GB disk which is full at 100%, or the large 1TB disk full at 71%? Becuase as you can see the parity disk is 1TB, so it should easily accommodate the second case.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The parity needs for each disk to be larger than the size of the files on that disk + overhead.
From what I see you have less than half a million files (I assume total). This would be what, 128GB overhead even considering one snapraid default block (256 KiB) for each file (even if there's more likely half a block on the average).
So really you shouldn't have any issue. On the other hand there was some other user reporting a week or two back some similar issue that went away when he gave up XFS (but he had it on the parity disk as well if I remember right). There might be some issue here with XFS, I don't have experience with it but it might be compression or some kind of snapshot/clones stored in it without much overhead - however presented to normal apps (like snapraid) as different files. Even if the disk is at 70% you could have (let's say) 2TB from a 1TB drive. Note that this is wild speculation.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
XFS doesn't have snapshots nor compression. And the 70% space occupied is on a 932G disk, so 70% * 932G = 661G. As per the "df -h" table from the fist post.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am trying to SnapRaid my setup, but I think it is failing due to too large number of files. Here's my setup:
All disks are XFS, apart form parity, which is formated with "mkfs.ext4 -m 0 -T largefile4 DEVICE"
Now, when I try to run snapraid -v sync, every time (after deleting failed content and parity files) it ends the same:
I had this problem before, but after deleting one folder, it went through. However, limiting number of files is not possible anymore.
Hi lockheed,
The issue is that the data disks are too filled, and there isn't space in the parity for all the files marked as "outofparity". If you move them to another data disk, you should be able to sync.
Ciao,
Andrea
Do you mean the small 320GB disk which is full at 100%, or the large 1TB disk full at 71%? Becuase as you can see the parity disk is 1TB, so it should easily accommodate the second case.
The parity needs for each disk to be larger than the size of the files on that disk + overhead.
From what I see you have less than half a million files (I assume total). This would be what, 128GB overhead even considering one snapraid default block (256 KiB) for each file (even if there's more likely half a block on the average).
So really you shouldn't have any issue. On the other hand there was some other user reporting a week or two back some similar issue that went away when he gave up XFS (but he had it on the parity disk as well if I remember right). There might be some issue here with XFS, I don't have experience with it but it might be compression or some kind of snapshot/clones stored in it without much overhead - however presented to normal apps (like snapraid) as different files. Even if the disk is at 70% you could have (let's say) 2TB from a 1TB drive. Note that this is wild speculation.
XFS doesn't have snapshots nor compression. And the 70% space occupied is on a 932G disk, so 70% * 932G = 661G. As per the "df -h" table from the fist post.