Talk:Journalling Flash File System
From DD-WRT Wiki
Revision as of 20:16, 23 February 2006 (edit) Atzekalle (Talk | contribs) (Reverted spam) ← Previous diff |
Current revision (23:44, 21 May 2008) (edit) (undo) S2s2 (Talk | contribs) (Article update) |
||
(27 intermediate revisions not shown.) | |||
Line 13: | Line 13: | ||
Filesystem 1k-blocks Used Available Use% Mounted on<br> | Filesystem 1k-blocks Used Available Use% Mounted on<br> | ||
/dev/root 2624 2624 0 100% /<br> | /dev/root 2624 2624 0 100% /<br> | ||
+ | |||
+ | --- | ||
enable jffs<br> | enable jffs<br> | ||
Line 21: | Line 23: | ||
BrainSlayer | BrainSlayer | ||
+ | |||
+ | == Unusable /jffs == | ||
+ | |||
+ | I have a WRT54GL, v.1.1, and I re-flashed it straight from Linksys, with dd-wrt.v23_mini_generic.bin The device works fine, but I would like to use the jffs. I tried all the things described in http://www.dd-wrt.com/wiki/index.php/Jffs, under the rubric "Enable JFFS when Flash Space is Available." I should have a few hundred K available for the /jffs. | ||
+ | |||
+ | The mount situation looks like this: | ||
+ | |||
+ | ~ # mount | ||
+ | |||
+ | /dev/root on / type squashfs (ro) | ||
+ | |||
+ | none on /dev type devfs (rw) | ||
+ | |||
+ | proc on /proc type proc (rw) | ||
+ | |||
+ | ramfs on /tmp type ramfs (rw) | ||
+ | |||
+ | /dev/mtdblock/4 on /jffs type jffs2 (rw) | ||
+ | |||
+ | ~ # df | ||
+ | |||
+ | Filesystem 1k-blocks Used Available Use% Mounted on | ||
+ | |||
+ | /dev/root 2880 2880 0 100% / | ||
+ | |||
+ | /dev/mtdblock/4 320 320 0 100% /jffs | ||
+ | |||
+ | The ls command shows a /jffs, but the filesystem is unusable. I can't create or copy a file into it, consistent with the line above, which shows /jffs 100% used. There is nothing visibly in there, other than an empty subdirectory, /jffs/tmp. | ||
+ | |||
+ | Could anyone figure out what I'm doing wrong? | ||
+ | |||
+ | == Article update == | ||
+ | |||
+ | 2008-05-22 | ||
+ | Last time I used CIFS, or tried to, it didn't work. There was some bug report about it and I do not know if it ever got resolved. | ||
+ | |||
+ | Those of us who do not want to dumb-down an entire server or NAS so simple SAMBA authentication works were working with CIFS. CIFS was tested from the client side quite successfully on a Linux box; however, the Linux box has more bells and whistles so there may be additional differences. I could not get the Busybox edition distributed with some v24 betas to work. | ||
+ | |||
+ | I updated the article. If someone wants to have a go at updating the Samba information to CIFS that would be great: must be a person who has actually gotten CIFS to work with current standards, i.e. Must have NTLMv2 as the default on their shares. | ||
+ | |||
+ | Regards. |
Current revision
That doesn't work for me... I've set these settings in the Webfrontend, the device rebooted, and that is what I get on the console...
BusyBox v1.00 (2005.05.10-21:26+0000) Built-in shell (ash) Enter 'help' for a list of built-in commands.
~ # mount
/dev/root on / type squashfs (ro)
none on /dev type devfs (rw)
proc on /proc type proc (rw)
ramfs on /tmp type ramfs (rw)
~ # df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/root 2624 2624 0 100% /
---
enable jffs
enable clean jffs
save settings
if this wont work, use the basic version. prefinal5 should also work with jffs support on G models, but prefinal4 has simply not enough flash space left
BrainSlayer
[edit] Unusable /jffs
I have a WRT54GL, v.1.1, and I re-flashed it straight from Linksys, with dd-wrt.v23_mini_generic.bin The device works fine, but I would like to use the jffs. I tried all the things described in http://www.dd-wrt.com/wiki/index.php/Jffs, under the rubric "Enable JFFS when Flash Space is Available." I should have a few hundred K available for the /jffs.
The mount situation looks like this:
~ # mount
/dev/root on / type squashfs (ro)
none on /dev type devfs (rw)
proc on /proc type proc (rw)
ramfs on /tmp type ramfs (rw)
/dev/mtdblock/4 on /jffs type jffs2 (rw)
~ # df
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/root 2880 2880 0 100% /
/dev/mtdblock/4 320 320 0 100% /jffs
The ls command shows a /jffs, but the filesystem is unusable. I can't create or copy a file into it, consistent with the line above, which shows /jffs 100% used. There is nothing visibly in there, other than an empty subdirectory, /jffs/tmp.
Could anyone figure out what I'm doing wrong?
[edit] Article update
2008-05-22 Last time I used CIFS, or tried to, it didn't work. There was some bug report about it and I do not know if it ever got resolved.
Those of us who do not want to dumb-down an entire server or NAS so simple SAMBA authentication works were working with CIFS. CIFS was tested from the client side quite successfully on a Linux box; however, the Linux box has more bells and whistles so there may be additional differences. I could not get the Busybox edition distributed with some v24 betas to work.
I updated the article. If someone wants to have a go at updating the Samba information to CIFS that would be great: must be a person who has actually gotten CIFS to work with current standards, i.e. Must have NTLMv2 as the default on their shares.
Regards.