Hi Mark,
Unfortunately, this is a known problem. saveData uses 32-bit file offsets within the MDA file.
I've been waiting for active development of scanSee (or of a scanSee replacement) to resume
before making any changes in the file format. In retrospect, that was probably not a wise choice.
Tim
________________________________________
From: [email protected] [[email protected]] on behalf of Mark Davis [[email protected]]
Sent: Friday, June 20, 2014 8:21 AM
To: [email protected]
Subject: saveData vs 2G file size limit
We have run in to a problem I was hoping someone has a simple answer for.
We are running sscan (vers 2-9) records and saveData on a 64-bit Linux
system (3.2.0-4-amd64 #1 SMP Debian 3.2.46-1 x86_64 GNU/Linux) and
recently discovered that scans hang when the mda file being written
reaches 2GB in size.
Given the version of Linux (64-bit 3.2 kernel) and the filesystem being
used (ext4), I am guessing that the limit is not imposed by the OS, but
either by a library or saveData.
Has anyone run in to this before? Is there an easy way to fix this?
Mark Davis
NSCL/FRIB
- References:
- saveData vs 2G file size limit Mark Davis
- Navigate by Date:
- Prev:
saveData vs 2G file size limit Mark Davis
- Next:
asyn R4-23 available Mark Rivers
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
<2014>
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
saveData vs 2G file size limit Mark Davis
- Next:
asyn R4-23 available Mark Rivers
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
<2014>
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
| 
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·