Your SlideShare is downloading. ×
Ayse Ozturk Sunum (0,2 MB)
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Ayse Ozturk Sunum (0,2 MB)

281
views

Published on


0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
281
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Logic anlat, difference in implementation
  • Add figure 2? Showing check regions
  • Transcript

    • 1. The Design Of Efficient Initialization And Crash Recovery For Log-based File Systems Over Flash Memory Chin-Hsien WU and Tei-Wei KUO;Li-Pin CHAN National Taiwan University; National Chiao-Tung University
    • 2. Flash technology considerations
      • Performance->
      • Quick mounting/unmounting
      • Effective garbage collection
      • Reliability->
      • Efficient roll-back
      • İnitialization and crash recovery
    • 3. Why Flash Memory?
      • Non-volatile
      • Shock-resistant
      • Power-economic
      • Affordable capacity
      • Suitable to mobile devices due to less energy need and
      • better vibration tolerance
    • 4. Features:
      • Write-once: updates to existing data on a page are only possible after an erase operation
      • No in-place updates
      • Out-place updates preferred for performance and endurance
    • 5. Different implementations
      • NFS(Native File System):
      • JFFS/2,LFM,YAFFS/2
      • *Access to files by vaiable sized records with (file-id and file-offset) pairs
      • Block-emulation approach:
      • FTL/Lite,CompactFlash,SmartMedia
      • *Access to files by indexes of LBA(Logical Block Addresses) and RAM resident address translation tables
    • 6. Mounting time:
      • Most important design consideration
      • Mount:scanning all spare areas of pages to reconstruct house-keeping data structures in main memory
      • Time consuming 
      • Will be impractical soon 
    • 7. Alternative way
      • Snapshot of entire housekeeping data structure
      • Speed up initialization 
      • What if crash or improper unmounting? 
    • 8. Proposed Solution
      • Log Management Scheme via Log-Record Manager(LRM) and Logger
      • For initialization and crash recovery scan check regions instead of all spare areas.
    • 9. LRM
      • Collect log-records in main memory
      • Write/Update to files
      • Merge/Delete as necessary
    • 10. Logger
      • Commit=write to flash memory log-records via check regions data structures
    • 11. Check regions
      • =#log segments and a log segment directory
      • Segments in size of a block
    • 12. Log-segment directory
      • Organization of check regions
    • 13. Visual representation-see article
    • 14. Related work
      • Effective garbage collection->cost-benefit policy by value-driven heuristic function
      • Periodically move live data among blocks to increase even erase counts
      • Adopt SRAM as write buffers, several cleaning polic,es
      • Interrupt emulation mechanism to reduce interference of IO on user tasks
      • Layers for index processing
      • Space efficient search-tree like structure for address translation
      • In-memory file system metadata(inode and cache)during unmounting write to flash memory.
      • If crash occurs, all spare areas need to be scanned 
      • Closest work to writer’s methodology
    • 15. Problem Formulation
      • Characteristics:
      • NAND flash
      • No overwrite->new data is written to free space->invalidate previous which is called dead
      • Block recycling policy minimize overhead due to live pages
      • 1 million erase counts max, then frequent write errors
      • Wear levelling->evenly erase blocks to increase lifetime
      • Wear-levelling if strong locality on updates causes too much overhead
    • 16. Initialization and Crash Recovery
      • Logical address space
      • by LBA(Logical Block Address) index
      • for block-device emulation via RAM-resident translation tables->mounting:rebuilt by scanning all spare areas
      • by (file id,offset pairs)for NFS->variable sized records to show writes/updates;hiearchical ds-tree in main memory to reflect updates;scan to construct logical view
    • 17. Problem
      • Scan time is intolerable to many users
      • Snapshot does not work well in case of crash and cause lengthy shut down procedure due to large fle size
    • 18. Solution
      • NFS is adapted in the solution which could be extended for block-emulation type.
      • NFS->writes, updates in sequential style(by appending)
      • BMI(back-up memory image) by scanning spare areas
      • PMI(primary memory image) by scanning check regions and stored in main memory
      • Additional log records are allowed as metadata about write/update operations on continous segment with starting offset and size
    • 19. System architecture
    • 20. Efficient Crash Recovery
      • Writes must be in appending fashion even inside a block
      • Committing log records in-order is required for the mechanism
      • Version tags to track the recency of data
      • In case of crash most recent and most consistent check region is used for recovery
    • 21. Intelligent scan
      • If first page of block is free, then skip the rest which is free due to in-order commitment policy
      • If metadata match some check region, then skip that part since already exists
      • Skipping some parts intelligently based on above logic reduces crash recovery time and provides better performance.
    • 22. Performance
      • Performance measurements with different metrics, ratio, buffer size and crash recovery scenarios show that the solution is efficient and has good performance on different cases.
    • 23. Conclusion
      • Reconstruction via check regions
      • Reduce crash recovery time
      • Improve initialization time with less overhead
      • Log-management scheme works well…
    • 24. Future Work
      • More performance enhancement
      • Even less overhead