Question

Bug Attaching 4.8TB Volume xmlReaderForFile failed

Laserfiche

Updated November 13, 2023

asked on November 10, 2023 • Show version history

I detached a volume from a 10.2.1.953 server environment to move and attach to a new 11.0.2102.175 environment.
The volume is a fixed volume 4.8TB. The detach completed.
During the attach process it exits immediately. The error file reads xmlReaderForFile failed. The volume did not attach any documents from the volume.

The toc XML is over 3.5Gb and notepad refuses to open it due to size. Notepad++ warns that it will take time to open as it is very large.

I also attempted to reattach the volume to the original repo to eliminate version issues and it still throws the same error.

0 0

Answer

SELECTED ANSWER

replied on November 13, 2023 • Show version history

We did indeed discover an undocumented size limit on attaching volumes in Laserfiche. No one knows what that limit is, but there is one. Laserfiche support verified that the XMLs were in tact and not corrupt. I had to restore the server and repack the files in smaller volumes. LF support recommended 20G volumes, but we did 50G volumes. At the end of the day we had to export and attach 97 volumes to restore the files.

2 0

Replies

replied on November 11, 2023

I've examined the headers and the footers of the xml file and they appear in tact.

0 0

replied on November 13, 2023 • Show version history

Unfortunately we don't return any specific information about what failed, but it looks like this error is more about reading the file at all than about the contents. The basic thing to check is that the file is readable by the server. Can you double-check that the path is correct, is reachable from the Laserfiche server, and that the server has permission to that location? Were you able to attach any other volumes, or is this the first one you've tried?

0 0

View 1 previous reply

SELECTED ANSWER

replied on November 13, 2023 • Show version history

2 0

replied on November 13, 2023

The support case is 235428 if anyone from Laserfiche wants to investigate further to help document the size limitation or eliminate the size limitation.

0 0

replied on November 13, 2023

Or create a process that will export an entire rollover and its volumes at once that imports as the same rollovers. Nobody wants to export 97 volumes and then import 97 volumes that then have to be migrated back into a different volume to be once again a nicely packaged rollover volume.

0 0

replied on November 13, 2023

The issue itself isn't due to the size of the exported volume per se. It's because at least one of the XML files generated from the volume export exceeds 2 GB.

We'll see if there's a way to improve the user experience in this regard. Thanks for the feedback.

2 0

You are not allowed to follow up in this post.

Question

Question

Bug Attaching 4.8TB Volume xmlReaderForFile failed

Answer

Replies

Sign in to reply to this post.