Scanned by Camscanner

Total Page:16

File Type:pdf, Size:1020Kb

Scanned by Camscanner Page 1 of 65. Scanned by CamScanner Broad Based Specifications of Vehicle for Scene of Crime Unit of National Cyber Forensic Laboratory for Evidentiary purpose S. No. Name of the Tool Specifications 2. Digital Forensic 1. Support collection of data from file systems including NTFS, FAT (12, 16 & 32 bit), EXFAT, HFS+, XFS, APFS, EXT2, EXT3 & Triage Tool Kit EXT4. 2. Support collection of data from both UEFI and BIOS based systems. 3. Support Profile configuration based on case. 4. Support digital forensic triage from powered off computers (Desktops, Laptops, Servers aka windows/linux/iOS)and running Windows computers(NTFS/FAT). 5. Support capture of volatile data/memory (RAM capture) 6. Support collection of Files from Removable Media (e.g. USB Drives) 7. Support collection of Files from Forensic Images (E01, DD etc.) 8. Support collection of files from Devices with Internal Memory Storage E.g. Digital Cameras. 9. Support physical backup to be supported by popular digital forensic tools. 10. Support extraction of data from Customised Locations. 11. Support data collection from mounted encrypted partitions. 12. Support automated analysis and report generation in PDF/HTML/DOCX of files collected from a target device. 13. Support automatic Logging (Device, Processing & User Interaction) of activities. 14. Support filter of data by Criteria to Target Specific Results. 15. Support Identify, Process and Display Browser History, Display Contents of E-Mail, Chat, Social Media Artefacts. 16. Support automatic indexing and tagging of hash and keyword matches. 17. Support time lining. 18. Solution in a ruggedized portable system with suitable processing and configuration as below: a. Processor family – intel core i7 or better b. RAM – 16GB DDR3 or more. c. SSD hard disk with 01TB capacity. d. Front integrated camera. e. 11.6” FHD (1920x1080) 16:9 Direct-View outdoor-readable display. f. 3 x USB 3.0, 1 x USB 3.1 (Type USB-C) Gen 1 supports power and display Micro Serial Port, Universal Audio Jack g. Intel Integrated HD Graphics h. Inbuilt supportive OS with dual boot to Windows 10. i. Lithium ion 2 cell primary as well as secondary battery along with suitable 3-prong AC adaptor. 19. Perpetual Licensing with 01 year warranty and Service Maintenance Support (SMS) with update/upgrade for a period of 02 years after warranty. Page 2 of 65. 20. Desirable: Solution should include certified training for 03 Experts from OEM with-in India or at OEM location. Page 3 of 65. Broad Based Specifications of the Faraday Bags for Scene of Crime Unit of National Cyber Forensic Laboratory for Evidentiary purpose S. No. Name of the Item Specifications 6. Faraday Bags 1. Should be able to isolate all types of RF connectivity i.e., Wi-Fi, Bluetooth, 2G, 3G, 4G LTE, GPS. 2. Should have sizes as below to suit various devices like laptops, notebooks, iPads, Mobiles, Drones etc.,: a. Width – 62 cm x height – 49cm b. Width – 46 cm x height – 32cm c. Width – 32 cm x height – 42cm d. Width – 22 cm x height – 28cm e. Width – 11.5 cm x height – 19cm f. Width – 17.5 cm x height – 24.5cm g. Width – 12.5 cm x height – 22cm h. Width – 125 cm x height – 60cm Page 4 of 65. Broad Based Specifications of the S/w and H/w Tools for Scene of Crime Unit of National Cyber Forensic Laboratory for Evidentiary purpose S. No. Name of the Tool Specifications 7. Imaging and write 1. Capable to acquire/clone data from one-to-one, two-to-two, one-to-two and two-to-one destinations media. blocking device. 2. Capable to acquire/clone data at the rate of 50 GB/Min or higher. 3. Capable to acquire/clone data in Drive to Drive and Drive to file/s format to support analysis in various forensic analysis tools. 4. Capable to cross copy support for various hard disk interfaces, USB interfaces. 5. Capable to authenticate the data with multiple hashing algorithms. 6. Capable to identify and acquire HPA and DCO areas of the suspect media. 7. Capable to acquire data directly from the live system with support for content-based image. 8. Capable to boot/mount the suspect media virtually in a write protected environment for preview of live data. 9. Capable to acquire data from suspect RAID (all RAID configurations) drives. 10. Capable to acquire data over a network. 11. Capable to generate the log of the processes. 12. Capable to search for the key words in the suspected media. 13. Include data and power interfaces to support all interfaces i.e., SATA, IDE, Fire wire, USB2, USB3, e-SATA, Micro-SATA, combine- SATA, SSDs and ZIF etc., along with their respective connecting cables. 14. Preloaded operating software. 15. Perpetual Licensing with 01 year warranty and Service Maintenance Support (SMS) with update/upgrade for a period of 02 years after warranty. 16. Desirable: Solution should include certified training for 03 Experts from OEM with in India or at OEM location. Page 5 of 65. Broad Based Specifications of the S/w and H/w Tools for Digital Storage Media Examination Unit of National Cyber Forensic Laboratory for Evidentiary purpose S. No. Name of the Tool Specifications 1. Hardware Forensic 1. Capable to acquire/clone data from one-to-one, two-to-two, one-to-two and two-to-one destinations media. Imaging Device. 2. Capable to acquire/clone data at the rate of 50 GB/Min or higher. 3. Capable to acquire/clone data in Drive to Drive and Drive to file/s format to support analysis in various forensic analysis tools. 4. Capable to cross copy support for various hard disk data interfaces, USB interfaces. 5. Capable to authenticate the data with multiple hashing algorithms. 6. Capable to identify and acquire HPA and DCO areas of the suspect media. 7. Capable to acquire data directly from the live system with support for content-based image. 8. Capable to boot/mount the suspect media virtually in a write protected environment for preview of live data. 9. Capable to acquire data from suspect RAID (all RAID configurations) drives. 10. Capable to acquire data over a network. 11. Capable to generate the log of the processes. 12. Capable to search for the key words in the suspected media. 13. Include data and power interfaces to support all interfaces i.e., SATA, IDE, Fire wire, USB2, USB3, e-SATA, Micro-SATA, combine- SATA, SSDs and ZIF etc., along with their respective connecting cables. 14. Preloaded operating software. 15. Perpetual Licensing with 01 year warranty and Service Maintenance Support (SMS) with update/upgrade for a period of 02 years after warranty. 16. Desirable: o Solution should include certified training for 03 Experts from OEM with in India or at OEM location. Page 6 of 65. Broad Based Specifications of the S/w and H/w Tools for Digital Storage Media Examination Unit of National Cyber Forensic Laboratory for Evidentiary purpose S. No. Name of the Tool Specifications 2. Hardware write 1. The kit should have Separate write-blocker devices to support vivid data interfaces i.e., SATA, IDE, Fire wire, USB2, USB3, e-SATA, Blocker Kit Micro-SATA, combine-SATA, SSDs and ZIF etc., along with their respective connecting cables. 2. Perpetual Licensing with 01 year warranty and Service Maintenance Support (SMS) with update/upgrade for a period of 02 years after warranty. Page 7 of 65. Broad Based Specifications of the S/w and H/w Tools for Digital Storage Media Examination Unit of National Cyber Forensic Laboratory for Evidentiary purpose S. No. Name of the Tool Specifications 3. Tool for acquisition 1. Support Acquisition of various devices like HDDs, Androids, iPhones, Cloud etc., of Data from HDDs, 2. Support analysis of data in an automated way by recovery, analysis and presentation of various artefacts from windows, iOS, mobiles. Smart Phones, Cloud 3. Support acquisition and analysis of volume shadow copies. and VSCs and 4. Support analysis of various Mobile logical and physical backups. automated 5. Support analysis of various artefacts from Windows, MAC, Unix based OSs. processing and 6. Support automated parsing of various internet artefacts, social networking app, instant messages and peer to peer data parsing. analysis of data 7. Support creation of portable cases for review purpose. specific criteria to 8. Support APFS, NTFS, iOS, FAT, EXT based file systems. internet and social 9. Support linkage analysis among files, users and devices. media artefacts. 10. Support time line analysis. 11. Support Data Analytics. 12. Support auto identification of password protected/encrypted containers and decrypting them with inbuilt or add-on module. 13. Support analysis of data basing on AI processing 14. Supports creation of customized reports. 15. Perpetual Licensing with 01 year warranty and Service Maintenance Support (SMS) with update/upgrade for a period of 02 years after warranty. 16. Desirable: o Solution should include certified training for 03 Experts from OEM with in India or at OEM location. Page 8 of 65. Broad Based Specifications of the S/w and H/w Tools for Digital Storage Media Examination Unit of National Cyber Forensic Laboratory for Evidentiary purpose S. No. Name of the Tool Specifications 4. Tool for digital 1. Support acquire, search, analyse, store and share digital evidence found inside computer and mobile devices, RAM and cloud. evidence processing 2. Support extract digital evidence from multiple sources by analysing hard drives, drive images, cloud, memory dumps, iOS, Blackberry and analysis. and Android backups, GrayKey, UFED, OFB, Elcomsoft, JTAG and chip-off dumps. 3. Support Windows (all versions, including Windows 10), macOS, Unix-based systems (Linux, FreeBSD, etc.), iOS (iPhone/iPad), Android, Windows Phone 8/8.1, Blackberry.
Recommended publications
  • Final Book Completed to Print in PRESS.Cdr
    S.Alagiavanan 3rd CSE GRAPHIC CARDS: V.Narendran 3rd CSE HOW THEY WORK voultion of computing over the last decade EVER Yet very few of you know exactly how these has seen a distinct differentiation based on marvels work. Today's graphic cards are the nature of the workload. On the one WONDERED marvels of engineering, with over 50 times the E raw computational power of current CPUs, but hand you have the computing heavy tasks while on the other, there are graphics intensive tasks. Rewind WHAT GOES they have far more specific and streamlined a back a decade, and you will remember almost every ON BEHIND task. There are two aspects to understanding other motherboard having a dedicated display port how a graphics card works. The first is to as the graphics processor was onboard. Also some THE SCENES understand how it works with the rest of the present day processors which sport integrated WHEN YOU components in a personal computer to generate graphics also have IGP ports on the board. But with an image. The second part would be to the graphical workloads getting more advanced and POWER UP understand the role of major components on outputs more realistic, you would need to invest in a video card. dedicated graphics processing unit to divide tasks YOUR between the CPU and the GPU. Another advantage GAME? of having a dedicated graphics processing unit is the fact that it lets your CPU be free to perform READ ON. other tasks. For instance you can rip a movie in the background while playing a game.
    [Show full text]
  • CS 152: Computer Systems Architecture Storage Technologies
    CS 152: Computer Systems Architecture Storage Technologies Sang-Woo Jun Winter 2019 Storage Used To be a Secondary Concern Typically, storage was not a first order citizen of a computer system o As alluded to by its name “secondary storage” o Its job was to load programs and data to memory, and disappear o Most applications only worked with CPU and system memory (DRAM) o Extreme applications like DBMSs were the exception Because conventional secondary storage was very slow o Things are changing! Some (Pre)History Magnetic core memory Rope memory (ROM) 1960’s Drum memory 1950~1970s 72 KiB per cubic foot! 100s of KiB (1024 bits in photo) Hand-woven to program the 1950’s Apollo guidance computer Photos from Wikipedia Some (More Recent) History Floppy disk drives 1970’s~2000’s 100 KiBs to 1.44 MiB Hard disk drives 1950’s to present MBs to TBs Photos from Wikipedia Some (Current) History Solid State Drives Non-Volatile Memory 2000’s to present 2010’s to present GB to TBs GBs Hard Disk Drives Dominant storage medium for the longest time o Still the largest capacity share Data organized into multiple magnetic platters o Mechanical head needs to move to where data is, to read it o Good sequential access, terrible random access • 100s of MB/s sequential, maybe 1 MB/s 4 KB random o Time for the head to move to the right location (“seek time”) may be ms long • 1000,000s of cycles! Typically “ATA” (Including IDE and EIDE), and later “SATA” interfaces o Connected via “South bridge” chipset Ding Yuan, “Operating Systems ECE344 Lecture 11: File
    [Show full text]
  • Scanned by Camscanner Annexure - 1 Broad Based Specifications for Forensic Platformfor National Cyber Forensic Laboratory
    Scanned by CamScanner Annexure - 1 Broad Based Specifications for Forensic Platformfor National Cyber Forensic Laboratory S. No. Name of the Tool Specifications 1. The integrated Integrated platform that enables centralized case management and web-based access to various digital forensic tools. Forensic Platform Interface to distributed processing support, Role Assignment, Password Cracking and Recovery, Wizard-Driven Multi-Machine, for sharing Customizable Processing. theDigital Forensic Integrated Simultaneous access to Forensic Lab, Attorneys and Investigators through centralised management console via web interface. tools with suitable Automate email notifications regarding case state. Should include the following with APIs APIs. o FTK Standalone Perpetual Licences – 10 Nos. o AccessData Lab - FTK Connection – 10 Nos. o AccessData Lab - Web User Account – 10 Nos. o Magnet AXIOM Complete Perpetual Licences – 10 Nos. o Comprehensive Mac and iOS forensic analysis and reporting software – 10 Nos. o Belkasoft Evidence Centre Perpetual Licences with integration – 10 Nos. o SPEKTOR Drive with 64GB USB drive running SPEKTOR software Black fabric case 1 x 1 TB collector 1 x 8GB USB Drive for exporting FIVE years' support and updates – 10 Nos. The solution should be deployed/operated on the inhouse Data Centre at CFSL, Hyderabad. The required server hardware and software components for the Integrated API is the responsibility of the solution provider. The platform should be flexible enough to accommodate more number of licences as per the need in future. Perpetual Licencing with 03 years warranty with support for updates up to 05 years. Solution should include certified training for 10 Experts from OEM with in India or at OEM location.
    [Show full text]
  • BEC Brochure for Partners
    3724 Heron Way, Palo Alto, CA 94303, USA +1 (650) 272-03-84 (USA and Canada) +7 (812) 926-64-74 (Europe and other regions) BELKASOFT EVIDENCE CENTER All-in-one forensic solution for locating, extracting, and analyzing digital evidence stored inside computers and mobile devices and mobile devices, RAM and cloud. Belkasoft Evidence Center is designed with forensic experts and investigators in mind: it automatically performs multiple tasks without requiring your presence, allowing you to speed up the investigation; at the same time, the product has convenient interface, making it a powerful, yet easy-to-use tool for data extraction, search, and analysis. INCLUDES Fully automated extraction and Advanced low-level expertise analysis of 1000+ types of evidence Concise and adjustable reports, Destroyed and hidden evidence accepted by courts recovery via data carving Case Management and a possibility Live RAM analysis to create a portable case to share with a colleague at no cost TYPES OF EVIDENCE SUPPORTED BY EVIDENCE CENTER Office documents System files, including Windows 10 Email clients timeline and TOAST, macOS plists, smartphone Wi-Fi and Bluetooth Pictures and videos configurations etc. Mobile application data Cryptocurrencies Web browser histories, cookies, cache, passwords, etc. Registry files Chats and instant messenger histories SQLite databases Social networks and cloud services Peer-to-peer software Encrypted files and volumes Plist files TYPES OF ANALYSIS PERFORMED BY EVIDENCE CENTER Existing files search and analysis. Low-level investigation using Hex Viewer Timeline analysis - ability to display and filter all user activities and system events in a single aggregated view Full-text search through all types of collected evidence.
    [Show full text]
  • Recursive Updates in Copy-On-Write File Systems - Modeling and Analysis
    2342 JOURNAL OF COMPUTERS, VOL. 9, NO. 10, OCTOBER 2014 Recursive Updates in Copy-on-write File Systems - Modeling and Analysis Jie Chen*, Jun Wang†, Zhihu Tan*, Changsheng Xie* *School of Computer Science and Technology Huazhong University of Science and Technology, China *Wuhan National Laboratory for Optoelectronics, Wuhan, Hubei 430074, China [email protected], {stan, cs_xie}@hust.edu.cn †Dept. of Electrical Engineering and Computer Science University of Central Florida, Orlando, Florida 32826, USA [email protected] Abstract—Copy-On-Write (COW) is a powerful technique recursive update. Recursive updates can lead to several for data protection in file systems. Unfortunately, it side effects to a storage system, such as write introduces a recursively updating problem, which leads to a amplification (also can be referred as additional writes) side effect of write amplification. Studying the behaviors of [4], I/O pattern alternation [5], and performance write amplification is important for designing, choosing and degradation [6]. This paper focuses on the side effects of optimizing the next generation file systems. However, there are many difficulties for evaluation due to the complexity of write amplification. file systems. To solve this problem, we proposed a typical Studying the behaviors of write amplification is COW file system model based on BTRFS, verified its important for designing, choosing, and optimizing the correctness through carefully designed experiments. By next generation file systems, especially when the file analyzing this model, we found that write amplification is systems uses a flash-memory-based underlying storage greatly affected by the distributions of files being accessed, system under online transaction processing (OLTP) which varies from 1.1x to 4.2x.
    [Show full text]
  • Title Smart Cites Forensics-Evaluating the Challenges of MK Smart City Forensics Name Ebenezer Okai
    Title Smart Cites Forensics-Evaluating the Challenges of MK Smart City Forensics Name Ebenezer Okai This is a digitised version of a dissertation submitted to the University of Bedfordshire. It is available to view only. This item is subject to copyright. INSTITUTE FOR RESEARCH IN APPLICABLE COMPUTING (IRAC) MASTERS BY RESEARCH MODE OF STUDY: FULL TIME Ebenezer Okai ID: 0708426 Smart Cites Forensics-Evaluating the Challenges of MK Smart City Forensics June 2019 I | P a g e Declaration “I, Ebenezer Okai declare that this thesis and the work presented in it are my own and has been generated by me as the result of my own original research. I confirm that: • This work was done wholly or mainly while in candidature for a research degree at this University; • Where any part of this thesis has previously been submitted for a degree or any other qualification at this University or any other institution, this has been clearly stated; • Where I have drawn on or cited the published work of others, this is always clearly attributed; • Where I have quoted from the work of others, the source is always given. With the exception of such quotations, this thesis is entirely my own work; • I have acknowledged all main sources of help; • Where the thesis or any part of it is based on work done by myself jointly with others, I have made clear exactly what was done by others and what I have contributed myself; • Either none of this work has been published before submission, or parts of this work have been published.
    [Show full text]
  • Yaffs Direct Interface
    Yaffs Direct Interface Charles Manning 2017-06-07 This document describes the Yaffs Direct Interface (YDI), which allows Yaffs to be simply integrated with embedded systems, with or without an RTOS. Table of Contents 1 Background.............................................................................................................................3 2 Licensing.................................................................................................................................3 3 What are Yaffs and Yaffs Direct Interface?.............................................................................3 4 Why use Yaffs?........................................................................................................................4 5 Source Code and Yaffs Resources ..........................................................................................4 6 System Requirements..............................................................................................................5 7 How to integrate Yaffs with an RTOS/Embedded system......................................................5 7.1 Source Files......................................................................................................................6 7.2 Integrating the POSIX Application Interface...................................................................9 8 RTOS Integration Interface...................................................................................................11 9 Yaffs NAND Model..............................................................................................................13
    [Show full text]
  • YAFFS a NAND Flash Filesystem
    Project Genesis Flash hardware YAFFS fundamentals Filesystem Details Embedded Use YAFFS A NAND flash filesystem Wookey [email protected] Aleph One Ltd Balloonboard.org Toby Churchill Ltd Embedded Linux Conference - Europe Linz Project Genesis Flash hardware YAFFS fundamentals Filesystem Details Embedded Use 1 Project Genesis 2 Flash hardware 3 YAFFS fundamentals 4 Filesystem Details 5 Embedded Use Project Genesis Flash hardware YAFFS fundamentals Filesystem Details Embedded Use Project Genesis TCL needed a reliable FS for NAND Charles Manning is the man Considered Smartmedia compatibile scheme (FAT+FTL) Considered JFFS2 Better than FTL High RAM use Slow boot times Project Genesis Flash hardware YAFFS fundamentals Filesystem Details Embedded Use History Decided to create ’YAFFS’ - Dec 2001 Working on NAND emulator - March 2002 Working on real NAND (Linux) - May 2002 WinCE version - Aug 2002 ucLinux use - Sept 2002 Linux rootfs - Nov 2002 pSOS version - Feb 2003 Shipping commercially - Early 2003 Linux 2.6 supported - Aug 2004 YAFFS2 - Dec 2004 Checkpointing - May 2006 Project Genesis Flash hardware YAFFS fundamentals Filesystem Details Embedded Use Flash primer - NOR vs NAND NOR flash NAND flash Access mode: Linear random access Page access Replaces: ROM Mass Storage Cost: Expensive Cheap Device Density: Low (64MB) High (1GB) Erase block 8k to 128K typical 32x512b / 64x2K pages size: Endurance: 100k to 1M erasures 10k to 100k erasures Erase time: 1second 2ms Programming: Byte by Byte, no limit on writes Page programming, must be erased before re-writing Data sense: Program byte to change 1s to 0s. Program page to change 1s to 0s. Erase block to change 0s to 1s Erase to change 0s to 1s Write Ordering: Random access programming Pages must be written sequen- tially within block Bad blocks: None when delivered, but will Bad blocks expected when deliv- wear out so filesystems should be ered.
    [Show full text]
  • FRASH: Hierarchical File System for FRAM and Flash
    FRASH: Hierarchical File System for FRAM and Flash Eun-ki Kim 1,2 Hyungjong Shin 1,2 Byung-gil Jeon 1,2 Seokhee Han 1 Jaemin Jung 1 Youjip Won 1 1Dept. of Electronics and Computer Engineering, Hanyang University, Seoul, Korea 2Samsung Electronics Co., Seoul, Korea [email protected] Abstract. In this work, we develop novel file system, FRASH, for byte- addressable NVRAM (FRAM[1]) and NAND Flash device. Byte addressable NVRAM and NAND Flash is typified by the DRAM-like fast access latency and high storage density, respectively. Hierarchical storage architecture which consists of byte-addressable NVRAM and NAND Flash device can bring synergy and can greatly enhance the efficiency of file system in various aspects. Unfortunately, current state of art file system for Flash device is not designed for byte-addressable NVRAM with DRAM-like access latency. FRASH file system (File System for FRAM an NAND Flash) aims at exploiting physical characteristics of FRAM and NAND Flash device. It effectively resolves long mount time issue which has long been problem in legacy LFS style NAND Flash file system. In FRASH file system, NVRAM is mapped into memory address space and contains file system metadata and file metadata information. Consistency between metadata in NVRAM and data in NAND Flash is maintained via transaction. In hardware aspect, we successfully developed hierarchical storage architecture. We used 8 MByte FRAM which is the largest chip allowed by current state of art technology. We compare the performance of FRASH with legacy Its-style file system for NAND Flash. FRASH file system achieves x5 improvement in file system mount latency.
    [Show full text]
  • Microsoft NTFS for Linux by Paragon Software 9.7.5
    Paragon Technologie GmbH Leo-Wohleb-Straße 8 ∙ 79098 Freiburg, Germany Tel. +49-761-59018-201 ∙ Fax +49-761-59018-130 Website: www.paragon-software.com E-mail: [email protected] Microsoft NTFS for Linux by Paragon Software 9.7.5 User manual Copyright© 1994-2021 Paragon Technologie GmbH. All rights reserved. Abstract This document covers implementation of NTFS & HFS+ file system support in Linux operating sys- tems using Paragon NTFS & HFS+ file system driver. Basic installation procedures are described. Detailed mount options description is given.File system creation (formatting) and checking utilities are described.List of supported NTFS & HFS+ features is given with limitations imposed by Linux. There is also advanced troubleshooting section. Information Copyright© 2021 Paragon Technologie GmbH All rights reserved. No parts of this work may be reproduced in any form or by any means - graphic, electronic, or mechanical, including photocopying, recording, taping, or information storage and re- trieval systems - without the written permission of the publisher. Products that are referred to in this document may be trademarks and/or registered trademarks of the respective owners. The publisher and the author make no claim to these trademarks. While every precaution has been taken in the preparation of this document, the publisher and the author assumes no responsibility for errors or omissions, or for damages resulting from the use of information contained in this document or from the use of programs and source code that may ac- company it. In no event shall the publisher and the author be liable for any loss of profit or any other commercial damage caused or alleged to have been caused directly or indirectly by this document.
    [Show full text]
  • Yaffs Robustness and Testing
    Yaffs Robustness and Testing Charles Manning 2017-06-07 Many embedded systems need to store critical data, making reliable file systems an important part of modern embedded system design. That robustness is not achieved through chance. Robustness is only achieved through design and extensive testing to verify that the file system functions correctly and is resistant to power failure. This document describes some of the important design criteria and design features used to achieve a robust design. The test methodologies are also described. Table of Contents 1 Background.............................................................................................................................2 2 Flash File System considerations............................................................................................3 3 How Yaffs achieves robustness and performance...................................................................5 4 Testing.....................................................................................................................................8 4.1 Power Fail Stress Testing.................................................................................................8 4.2 Testing the Yaffs Direct Interface API..............................................................................9 4.3 Linux Testing....................................................................................................................9 4.4 Fuzz Testing......................................................................................................................9
    [Show full text]
  • Journaling File Systems
    JOURNALING FILE SYSTEMS CS124 – Operating Systems Spring 2021, Lecture 26 2 File System Robustness • The operating system keeps a cache of filesystem data • Secondary storage devices are much slower than main memory • Caching frequently-used disk blocks in memory yields significant performance improvements by avoiding disk-IO operations • ProBlem 1: Operating systems crash. Hardware fails. • ProBlem 2: Many filesystem operations involve multiple steps • Example: deleting a file minimally involves removing a directory entry, and updating the free map • May involve several other steps depending on filesystem design • If only some of these steps are successfully written to disk, filesystem corruption is highly likely 3 File System Robustness (2) • The OS should try to maintain the filesystem’s correctness • …at least, in some minimal way… • Example: ext2 filesystems maintain a “mount state” in the filesystem’s superBlock on disk • When filesystem is mounted, this value is set to indicate how the filesystem is mounted (e.g. read-only, etc.) • When the filesystem is cleanly unmounted, the mount-state is set to EXT2_VALID_FS to record that the filesystem is trustworthy • When OS starts up, if it sees an ext2 drive’s mount-state as not EXT2_VALID_FS, it knows something happened • The OS can take steps to verify the filesystem, and fix it if needed • Typically, this involves running the fsck system utility • “File System Consistency checK” • (Frequently, OSes also run scheduled filesystem checks too) 4 The fsck Utility • To verify the filesystem,
    [Show full text]