Size of Session Folder dangers?
Hi All!
I was just wondering, given that C1 (build 15 3 2 11) is getting a bit tetchy* of late, does the size of a session cause any problems with the sweet running of C1?
I have a large and growing project (session database is 28Mb, the capture folder is getting close to 64Gb), the capture folder is populated in date named assets folders where the day's shoot is curated.
Is there any evidence, empirical or anecdotal, that suggests that large session folders are problematic?
Thanks!
*had a database that needed verifying and repairing but the dialogue pane got stuck three times on, and I quote:
Page 3617 is never used
NULL
The only way out was to close the app and restart. Eventually it sorted itself out.
UPDATE
Happened again, about half an hour later. This time I have:
Page 4368: unable to get the page. error code=266
NULL
This is blinking and nver moves on, so I have to quite.
Might be of interest, I am running this session folder (complete) from a 500 Gb Sandisk SSD.
-
>John Wildgoose: ...unable to get the page. error code=266
That could be a SQLite message, potentially while performing an integrity check. It is not possible to make much sense of it in isolation. Is the session database located on an internal or external disk? You may be able to find more details in system logs or C1 logs. I have seen error 266 discussed in context of hardware trouble and also with file locking where more than one application try to access the same database file. If my memory serves me right, anti virus software may have be involved in some of the cases.
I do not think the size of the cosessiondb file should be an issue, 28MB is close to nothing.
0 -
Thanks for the rapid reply!
I have a feeling that it's a hardware issue. I tried to run first aid on the drive and it failed - forget the reason why, but I recall it was something to do with permissions, which is crazy as none were set. So I am thinking there's a corruption. So (nervously) moved the entire folder set onto a G-Tech HD and it all seemed fine, and I worked on the sessions for longer than I could with the Sandisk SSD.
Pity. I really liked those little SSDs, so handy when traveling. I guess I'll get a Samsung T7 as it's small and I've had a few and they have never presented any issues (kiss of death comment).
Thanks again OddS
0 -
Dug deeper and it seems there's a whole host of issues with Monterey and SSDs, people screaming at Apple for causing the issues. I checked all my ports and cables and they work fine BUT ONLY on HDs. I checked three G-Tech SSDs (2x 500 and 1x 1Tb) and they will not mount, my M1 Pro will not recognise them. I thought about it being a G-Tech issue, and was going to try the Sandisk again and then I remembered that some times, for no reason, that SSD would unmount and I'd get a note to say it had been disconnected without being unmounted properly. I have been able to format/erase this in D Utillities so I'll check if it's still not performing as it should.
So I am figuring this is an Apple issue, I feel like the ports are under powered, or there's some code somewhere that doesn't like SSDs. All my SSDs worked fine on Intel Macs, all worked fine pre Monterey. Now it's screwed, royally. I've heard people formatting these drives on an earlier OS, and then they work on the M1/Monterey.Mad. But at least I know the issues. Ok using HDs for Capture One, but it's going to be a deal breaker for Final Cut Pro projects.
0
Post ist für Kommentare geschlossen.
Kommentare
3 Kommentare