Hi,
We are using an old version of YAFFS in an embedded application (ARM
processor, NAND flash).
We 'inherited' the YAFFS sources from the supplier of the OS so can't
ascertain the version of YAFFS
- not sure if this helps anyone identify the version but the copyright
notice at the top of the files reads:-
* Copyright (C) 2002 Aleph One Ltd.
* for Toby Churchill Ltd and Brightstar Engineering
*
* Created by Charles Manning <
charles@aleph1.co.uk>
Currently having problems with file system corruption and currently
analysing the source files to try and
establish whether the OS wrapper code (suspect this) or the YAFFS code is
the root of the problem.
My question is:-
Have read the 'YAFFS:HowItWorks' document and understand the file system
is scanned and re-built
each time it restarts but can't quite see how garbage collection is
triggered.
Have perused the archive mailing list back to start of 2012 and have seen
some evidence to suggest
garbage collection gets triggered at a filesystem write.
Can someone confirm that garbage collection is triggered each time the
filesystem is written to or
clarify just when it does occur ?
Regards
_____________________________________________________________________________________
Tom Edmond | Schneider Electric | Infrastructure Business |
United Kingdom | Senior Systems Development Engineer
Phone: +44 (0) 1249 456116 | Fax: +44 (0) 1249 456150 |
Email:
tom.edmond@schneider-electric.com | Site:
www.schneider-electric.com | Address: Connect 17 Building, Langley
Park, Langley Road, Chippenham, Wiltshire, SN15 1GG
Schneider Electric Limited is a company registered in England and Wales.
Registered number: 1407228. Registered office: Stafford Park 5, Telford,
Shropshire TF3 3BL.
This message (and any associated files) is intended only for the use of
the intended recipient and may contain information that is confidential,
subject to copyright or constitutes a trade secret.
If you are not the intended recipient you are hereby notified that any
dissemination, copying or distribution of this message, or files
associated with this message, is strictly prohibited.
If you have received this message in error, please notify us immediately
by replying to the message and deleting it from your computer.
Any views or opinions presented are solely those of the author and do not
necessarily represent those of the company.
*** Please consider the environment before printing this e-mail
(text/plain)