View Single Post
  #1475 (permalink)  
Old 04-12-2012, 07:22 PM
arrrghhh's Avatar
arrrghhh
Testing Extraordinaire
Offline
 
Join Date: Mar 2007
Posts: 3,604
Reputation: 7360
arrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the communityarrrghhh is a trusted member of the community
Mentioned: 7 Post(s)
Tagged: 0 Thread(s)
Re: [TESTING] - NAND OMGB (1.2.3)

Quote:
Originally Posted by wizardknight View Post
A good battery driver would make me take the jump to NAND. I do hope we get a release soon that has this in it.

A question to those running NAND. Any issues with forced reboots corrupting data? I know that the data.img file can be corrupted sometimes on the SD side of things if you lock up and have to force a reboot. I didn't think there were similar issues with NAND, but I thought I would ask.
Quote:
Originally Posted by rwar View Post
No issue here with forced reboots corrupting data
Quote:
Originally Posted by htrakr View Post
There are reboots (rarely but it does happen especially if you have a lot running). There is no data corruption
Data corruption that is experienced on the SD builds is pretty much impossible to experience on NAND - we can't properly unmount the partitions on SD builds, and therefore the data partition/image file always ends up in a dirty state. That and it's all running on FAT32, don't even get me started on what a nightmare that is in practice.

So eliminating those factors have eliminated the data corruption. I've never experienced it on NAND, nor would I ever expect to experience it.
Reply With Quote
This post has been thanked 1 times.