- This topic has 15 replies, 3 voices, and was last updated Dec 10-10:32 pm by olsztyn.
-
Posts
-
olsztyn
I apologize if this has been discussed and I just missed it searching forum posts…
My experience is that whenever I try to specify an SMB share (attached using Connectshares) as destination for ISO-Snapshot output, it seems to start squashing but then it comes back with Fatal Error: Failed to write to output file system. The error window says ‘Could not create linuxfs file, please check if you have enough space on the destination partition’.
The most current test is using the fully updated Live antiX 19.2 Hannie Schaft.
This is not a significant issue as creating ISO-Snapshot on Live-USB-Storage appears to work fine, so such snapshot can be moved to SMB share after ISO-Snapshot is done.
Therefore is is just a question whether it is expected that ISO-Snapshot is not working with SMB shares as destination…
Thanks and Regards…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersAnonymous
Possibly the latency when writing to the remote destination is triggering this never-patched-in-debian bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1785652
^—v
https://kernel.googlesource.com/pub/scm/fs/squashfs/squashfs-tools/+/de03266983ceb62e5365aac84fcd3b2fd4d16e6f
^—v
https://kernel.googlesource.com/pub/scm/fs/squashfs/squashfs-tools/+/de03266983ceb62e5365aac84fcd3b2fd4d16e6f%5E%21/#F0In the link below, notice the absence of the line
pthread_mutex_unlock(&fragment_mutex);https://sources.debian.org/src/squashfs-tools/1:4.3-12/squashfs-tools/mksquashfs.c/#L2453
__________
edited to add:
> never-patched-in-debian
is an unqualified description. I only checked the debian10 (buster) packaged version of squashfs-tools.
A version which incorporates the patch may be available from sid//experimental//backports
anticapitalista
What format is your SMB share?
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Thank you skidoo for identifying what appears to be most likely cause of this… So it seems RedHat is patched and Debian is not, if I understand…
Thanks and Regards…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parametersanticapitalista
Thank you skidoo for identifying what appears to be most likely cause of this… So it seems RedHat is patched and Debian is not, if I understand…
Thanks and Regards…Plus 1 from me to skidoo!
I’ll see if we can add the patch for antiX users.Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
What format is your SMB share?
Not sure if this is what your question refers to:
SMB 2.0 on NAS server RAID1.
Access authenticated through Connectshares and share is showing in SpaceFM and is accessible.
Thanks and Regards.Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parametersanticapitalista
@olsztyn – please test the bugfix deb here and let us know so if it works, we can move it to our repos.
https://download.tuxfamily.org/antix/Testing/
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Installed the new squashfs-tools ver. 4.3-12.0antix1 (64bit) and re-executed ISO-Snapshot to SMB share as output destination. Unfortunately it is resulting in the same error. From execution log it seems it is abending on creating 4.0 filesystem on iso-template/antiX/linuxfs.
Again, it is not an important issue and workaround is to output to Live-USB-Storage and then move to SMB share. So it might not be worth to spend precious time to fix it…
Just to clarify:
I executed ISO-Snapshot right after squashfs-tools update, I did not reboot. So if squashfs-tools gets pre-loaded in memory on boot and is not refreshed then the old version might have been executed. I do not suppose this would be the case though…- This reply was modified 2 years, 4 months ago by olsztyn.
Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parametersanticapitalista
Thanks for the feedback.
Can you try again after a reboot.
Thanks.Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
Can you try again after a reboot.
Remastered and rebooted (running without persistence).
ISO-Snapshot still results in the same error with new squashfs-tools…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameterssuggested next step:
inquire with the the author of the mksquashfs program, Phillip Lougher, here:
https://github.com/plougher/squashfs-tools/issuesThank you skidoo for this suggestion.
I will do this after I figure out how to articulate such question so it is more generically related to mksquashfs and not to antiX ISO-Snapshot.
Thanks and Regards.Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersThe call to the underlying mksquashfs command occurs here: mainwindow.cpp#L639
but the call is rather generic ~~ the variable mksq_opt, by default it is blank. So, unless you had personally edited iso-snapshot.conf to specify custom options (many are available, per mksquashfs manpage), the operation is not asking to do anything extraordinary.I think I understand the call to mksquashfs appears generic, so agree with your argumentation on this. My extended consideration is that the output is on the network rather than local fs, which might make a difference, whether for mksquashfs or within antiX architecture. So if mksquashfs is agnostic of output location as long as it is addressed by the host system, then this could potentially point to how it is handled in antiX or Debian architecture to map the output of mksquashfs to network location.
I hope I am more clear now that it might be not clear that the difference of handling of output location – local vs. network potentially may not be specific to mksquashfs design.Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_ParametersHi skidoo.
I posted this question to the forum you pointed me to… The link is the following:
https://github.com/plougher/squashfs-tools/issues/99Text of the post inline for your convenience:
”
Executing ISO-Snapshot tool, which calls mksquashfs to create a squashed file output is successful when the output location is local but results in fatal error when output location is on network SMB share.
Is this a known limitation of mksquashfs or is this supposed to work and the cause of the issue is elsewhere?
Environment details:Debian based antiX linux. ISO-Snapshot tool takes a snapshot of running system and creates squashed output.
Location of output is on SMB 2.0 (or 2.1) share. Share is visible and accessible from file manager (SpaceFM).
Any help in resolving this will be greatly appreciated…
Thanks and Regards.
”
Please let me know if the inquiry post is incorrectly articulated…Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters
- You must be logged in to reply to this topic.
