Xent node beem GCed issue
=?gb2312?B?TGluZ2VyIExlZSAowO695+RoKQ==?=
linger.lee at mediatek.com
Mon Apr 14 03:03:19 PDT 2014
Hi all,
I found a issue about Xent node been GCed and fail in ubifs_tnc_remove_ino function
Got error message “bad node type (255 but expected 3)”
The situation is
1. Create a file and set xattr (you get dent node A, inode B, xent C, xattr inode D)
2. Unlink the file (got A w/ ino 0, inode B w/ nlink 0 in log)
3. GC the LEB where C/D is belong to and write new data on the LEB
4. Reboot w/o commit
5. Then ubifs_tnc_remove_ino get the index of node C, but can’t get the node C (bad node happened)
We can’t mount the volume anymore
Suggestion: In Step 2, we maybe need log more (C w/ ino 0 and D w/ nlink 0)
Cheers,
Linger
************* Email Confidentiality Notice ********************
The information contained in this e-mail message (including any
attachments) may be confidential, proprietary, privileged, or otherwise
exempt from disclosure under applicable laws. It is intended to be
conveyed only to the designated recipient(s). Any use, dissemination,
distribution, printing, retaining or copying of this e-mail (including its
attachments) by unintended recipient(s) is strictly prohibited and may
be unlawful. If you are not an intended recipient of this e-mail, or believe
that you have received this e-mail in error, please notify the sender
immediately (by replying to this e-mail), delete any and all copies of
this e-mail (including any attachments) from your system, and do not
disclose the content of this e-mail to any other person. Thank you!
More information about the linux-mtd
mailing list