Thanks for suggesting me on timestamp update.
How can I know the physical location of a file accessed for reading or
writing ? I get a messages on console " ecc error fix performed on chunk
8573:0 " on the console. Is there any possibility to determine the location
where this ecc fix is performed (offset from where the flash is mapped ).
The number 8573 is the chunk id, I suppose. Is there any logic to find out
the physical location of the chunk, I suppose the page ?
Any reference docs or ideas would help me to figure it out.
Thanks,
Chandru.
-----Original Message-----
From:
yaffs-bounces@lists.aleph1.co.uk
[
mailto:yaffs-bounces@lists.aleph1.co.uk] On Behalf Of
yaffs-request@lists.aleph1.co.uk
Sent: Tuesday, January 16, 2007 5:31 PM
To:
yaffs@lists.aleph1.co.uk
Subject: yaffs Digest, Vol 20, Issue 7
Send yaffs mailing list submissions to
yaffs@lists.aleph1.co.uk
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs
or, via email, send a message with subject or body 'help' to
yaffs-request@lists.aleph1.co.uk
You can reach the person managing the list at
yaffs-owner@lists.aleph1.co.uk
When replying, please edit your Subject line so it is more specific
than "Re: Contents of yaffs digest..."
Today's Topics:
1. mount without updating timestamp (Chandru)
2. Re: Where is the archive? (Wookey)
3. Re: mount without updating timestamp (Charles Manning)
4. Build error on 2.6.19 and my thoughts about the source code
(Aubrey Li)
5. Build error on 2.6.19 and my thoughts about the source code
(Aubrey Li)
6. problem with my nand driver (Chuck Tilbury)
----------------------------------------------------------------------
Message: 1
Date: Mon, 15 Jan 2007 17:50:27 +0530
From: "Chandru" <
chandrasekar@aelixsystems.com>
Subject: [Yaffs] mount without updating timestamp
To: <
yaffs@lists.aleph1.co.uk>
Message-ID: <
mailman.0.1168948825.18960.yaffs@lists.aleph1.co.uk>
Content-Type: text/plain; charset="us-ascii"
Hi,
I am using yaffs file system with 2.4.19 kernel. I want to mount
the file system, where in I don't want the timestamp to be updated when a
file is accessed for reading and writing.
Can anybody suggest me an idea ?
Thanks,
Chandru.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://aleph1.co.uk/lurker/list/yaffs.html/attachments/20070115/36ddb729/att
achment.html
------------------------------
Message: 2
Date: Mon, 15 Jan 2007 18:18:32 +0000
From: Wookey <
wookey@aleph1.co.uk>
Subject: [Yaffs] Re: Where is the archive?
To: Chuck Tilbury <
chuck@whistlemaker.com>
Cc:
yaffs@lists.aleph1.co.uk
Message-ID: <20070115181831.GR31021@xios>
Content-Type: text/plain; charset=us-ascii
On 2007-01-14 18:45 -0800, Chuck Tilbury wrote:
>
> Can anyone give me a pointer to the archive? The link in the signup page
does
> not seem to work.
Hmm, yes something has gone wrong there. The lurker archive indexing
has gone puff. It looks like it stopped working when the new year
rolled over into 2007. Thanx for pointing that out. I'll fix it and
post here when it's done.
(there is a secondary issue that the URL on the signup page has a
trailing '/' which is not wanted).
In the meantime you can read the old archives here:
http://aleph1.co.uk/pipermail/yaffs/
but they only go up to aug 3rd last year, and thus probably don't
contain what you want.
Apologies for the outage.
Wookey
--
Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK Tel +44 (0) 1223 811679
work: http://www.aleph1.co.uk/ play: http://wookware.org/
------------------------------
Message: 3
Date: Tue, 16 Jan 2007 13:39:31 +1300
From: Charles Manning <
manningc2@actrix.gen.nz>
Subject: Re: [Yaffs] mount without updating timestamp
To:
yaffs@lists.aleph1.co.uk
Cc: Chandru <
chandrasekar@aelixsystems.com>
Message-ID: <
200701161339.32007.manningc2@actrix.gen.nz>
Content-Type: text/plain; charset="utf-8"
On Tuesday 16 January 2007 01:20, Chandru wrote:
> Hi,
>
> I am using yaffs file system with 2.4.19 kernel. I want to
> mount the file system, where in I don't want the timestamp to be updated
> when a file is accessed for reading and writing.
>
> Can anybody suggest me an idea ?
In file system technical speak I think you mean mounting with noatime.
atime is updated when a file is accessed. This slows the file system. Thus,
you can mount a file system with a noatime flag which prevents the flag from
being updated whenever the file is read.
YAFFS does not support atime updating. Any time you mount yaffs it is
equivalent to mounting with noatime.
YAFFS does however update file times when the files are written. The only
way
I can think of to get around this is to programmatically set the file update
time after you have written the file.
-- CHarles
------------------------------
Message: 4
Date: Tue, 16 Jan 2007 12:42:37 +0800
From: "Aubrey Li" <aubreylee@gmail.com>
Subject: [Yaffs] Build error on 2.6.19 and my thoughts about the
source code
To: yaffs@lists.aleph1.co.uk, yaffs@stoneboat.aleph1.co.uk
Message-ID:
<6d6a94c50701152042i3e72692o7cb5242710ba48c6@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi all,
The error I encounted is exactly as Claudio Lanconelli's post here
several days ago.
=====================================================
fs/yaffs2/yaffs_fs.c: In function `yaffs_readlink':
fs/yaffs2/yaffs_fs.c:263: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c:267: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_follow_link':
fs/yaffs2/yaffs_fs.c:287: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c:291: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_lookup':
fs/yaffs2/yaffs_fs.c:328: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c:332: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c:337: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_clear_inode':
fs/yaffs2/yaffs_fs.c:396: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c:411: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_delete_inode':
fs/yaffs2/yaffs_fs.c:432: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_file_flush':
fs/yaffs2/yaffs_fs.c:458: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_readpage_nolock':
fs/yaffs2/yaffs_fs.c:489: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_writepage':
fs/yaffs2/yaffs_fs.c:589: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_FillInodeFromObject':
fs/yaffs2/yaffs_fs.c:707: error: structure has no member named `i_blksize'
fs/yaffs2/yaffs_fs.c:759: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_file_write':
fs/yaffs2/yaffs_fs.c:808: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_readdir':
fs/yaffs2/yaffs_fs.c:868: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_mknod':
fs/yaffs2/yaffs_fs.c:962: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_unlink':
fs/yaffs2/yaffs_fs.c:1077: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c:1081: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_link':
fs/yaffs2/yaffs_fs.c:1107: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c:1115: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_symlink':
fs/yaffs2/yaffs_fs.c:1150: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c:1152: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_sync_object':
fs/yaffs2/yaffs_fs.c:1179: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_rename':
fs/yaffs2/yaffs_fs.c:1203: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c:1209: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c:1227: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c:1229: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_setattr':
fs/yaffs2/yaffs_fs.c:1254: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c:1260: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c:1262: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_statfs':
fs/yaffs2/yaffs_fs.c:1278: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: At top level:
=====================================================
Has the patch been applied in CVS?
Another issue is my thoughts about the source code.
In my opinion, the current source code is terrible. KERNEL VERSION
macros is everywhere. I hate it very much. It caused the code ugly.
Since we have the CVS, why not maintain it by cvs tag/branch? for
example tag_2-6-18 for kernel(2,6,18), tag_2-6-19 for kernel(2,6,19)?
If we still add kernel version control in the source code, the code
will become more and more un-maintainable soon.
-Aubrey
------------------------------
Message: 5
Date: Tue, 16 Jan 2007 12:42:37 +0800
From: "Aubrey Li" <aubreylee@gmail.com>
Subject: [Yaffs] Build error on 2.6.19 and my thoughts about the
source code
To: yaffs@lists.aleph1.co.uk, yaffs@stoneboat.aleph1.co.uk
Message-ID:
<6d6a94c50701152042i3e72692o7cb5242710ba48c6@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi all,
The error I encounted is exactly as Claudio Lanconelli's post here
several days ago.
=====================================================
fs/yaffs2/yaffs_fs.c: In function `yaffs_readlink':
fs/yaffs2/yaffs_fs.c:263: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c:267: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_follow_link':
fs/yaffs2/yaffs_fs.c:287: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c:291: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_lookup':
fs/yaffs2/yaffs_fs.c:328: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c:332: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c:337: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_clear_inode':
fs/yaffs2/yaffs_fs.c:396: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c:411: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_delete_inode':
fs/yaffs2/yaffs_fs.c:432: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_file_flush':
fs/yaffs2/yaffs_fs.c:458: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_readpage_nolock':
fs/yaffs2/yaffs_fs.c:489: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_writepage':
fs/yaffs2/yaffs_fs.c:589: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_FillInodeFromObject':
fs/yaffs2/yaffs_fs.c:707: error: structure has no member named `i_blksize'
fs/yaffs2/yaffs_fs.c:759: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_file_write':
fs/yaffs2/yaffs_fs.c:808: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_readdir':
fs/yaffs2/yaffs_fs.c:868: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_mknod':
fs/yaffs2/yaffs_fs.c:962: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_unlink':
fs/yaffs2/yaffs_fs.c:1077: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c:1081: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_link':
fs/yaffs2/yaffs_fs.c:1107: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c:1115: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_symlink':
fs/yaffs2/yaffs_fs.c:1150: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c:1152: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_sync_object':
fs/yaffs2/yaffs_fs.c:1179: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_rename':
fs/yaffs2/yaffs_fs.c:1203: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c:1209: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c:1227: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c:1229: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_setattr':
fs/yaffs2/yaffs_fs.c:1254: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c:1260: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c:1262: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: In function `yaffs_statfs':
fs/yaffs2/yaffs_fs.c:1278: error: structure has no member named `u'
fs/yaffs2/yaffs_fs.c: At top level:
=====================================================
Has the patch been applied in CVS?
Another issue is my thoughts about the source code.
In my opinion, the current source code is terrible. KERNEL VERSION
macros is everywhere. I hate it very much. It caused the code ugly.
Since we have the CVS, why not maintain it by cvs tag/branch? for
example tag_2-6-18 for kernel(2,6,18), tag_2-6-19 for kernel(2,6,19)?
If we still add kernel version control in the source code, the code
will become more and more un-maintainable soon.
-Aubrey
------------------------------
Message: 6
Date: Mon, 15 Jan 2007 22:47:03 -0800
From: Chuck Tilbury <
chuck@whistlemaker.com>
Subject: [Yaffs] problem with my nand driver
To:
yaffs@lists.aleph1.co.uk
Message-ID: <
200701152247.03111.chuck@whistlemaker.com>
Content-Type: text/plain; charset="us-ascii"
I am having a weird problem with my nand driver. Since I am using yaffs and
I
have that spew, I hope it is OK that I post here. Let me know if it's not.
When I copy a file to the file yaffs file system, I get a lot of spew that
looks like this:
**>> Block 1 needs retiring
**>> Block 2 needs retiring
**>> Block 2 retired
**>> Block 3 needs retiring
**>> Block 3 retired
**>> Block 4 needs retiring
**>> Block 4 retired
..... messages with sequential block numbers deleted ......
**>> Block 779 needs retiring
**>> Block 779 retired
**>> yaffs write required 780 attempts
**>> Block 1 retired
# ls -las /mnt
0 drw-rw-rw- 1 0 0 512 .
1 drwxrwxrwx 14 0 0 1024 ..
0 drw-rw-rw- 1 0 0 512 lost+found
0 -rw-r--r-- 1 0 0 426 rc
The file /etc/rc was written correctly to the FS.
When I turn on any debugging, it does not retire blocks at all. In fact, if
I
insert a printk() anywhere such that it gets called once in a while, the
retire messages go away and the status in /proc/yaffs shows that no blocks
were retired. If I get rid of all of the debugging messages, I run out of
space in a few writes. (it's a 64M byte part)
With all debugging on, I get this spew:
# cp /etc/inittab /mnt
yaffs_mknod: making oject for inittab, mode 81a4 dev 0
Writing chunk 24931 tags 262 0
Chunk -1 not found zero instead
Chunk -1 not found zero instead
Chunk -1 not found zero instead
Chunk -1 not found zero instead
Chunk -1 not found zero instead
Chunk -1 not found zero instead
Chunk -1 not found zero instead
Chunk -1 not found zero instead
Chunk -1 not found zero instead
Writing chunk 24932 tags 262 1
Writing chunk 24933 tags 262 0
line 3142 delete of chunk 24963
Writing chunk 24931 tags 0 0
# ls -las /mnt
yaffs_readdir: starting at 0
yaffs_readdir: starting at 5
0 drw-rw-rw- 1 0 0 512 .
1 drwxrwxrwx 14 0 0 1024 ..
0 -rw-r--r-- 1 0 0 82 inittab
0 drw-rw-rw- 1 0 0 512 lost+found
0 -rw-r--r-- 1 0 0 426 rc
Again a correct write.
I have been messing around with the timing on the GPIO lines that control
the
part and I always come back to this. Can anyone give a pointer? Is
the "Chunk -1 ..." message an indication of a failure?
Thanks guys,
-=ChuckT=-
------------------------------
_______________________________________________
yaffs mailing list
yaffs@lists.aleph1.co.uk
http://lists.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs
End of yaffs Digest, Vol 20, Issue 7
************************************
__________ NOD32 1979 (20070115) Information __________
This message was checked by NOD32 antivirus system.
http://www.eset.com
(text/plain)