Modify

Opened 3 years ago

Closed 3 years ago

#17526 closed defect (too_vague)

Brcm47xx wrong overlayfs device - unable to save changes

Reported by: anonymous Owned by: developers
Priority: high Milestone: Barrier Breaker 14.07
Component: base system Version: Trunk
Keywords: Cc:

Description

On a freshly flashed WRT54GL (14.07rc3/snapshot and/or Image Generator) the mounting table looks like this:

rootfs on / type rootfs (rw)
/dev/root on /rom type squashfs (ro,relatime)
proc on /proc type proc (rw,noatime)
sysfs on /sys type sysfs (rw,noatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime)
tmpfs on /tmp/root type tmpfs (rw,noatime,mode=755)
overlayfs:/tmp/root on / type overlayfs (rw,noatime,lowerdir=/,upperdir=/tmp/root)
tmpfs on /dev type tmpfs (rw,relatime,size=512k,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
debugfs on /sys/kernel/debug type debugfs (rw,noatime)

As previously posted, an mounting an overlayfs containing config data on volatile ram is ... volatile - pardon brainl... - pardon useless.

Attachments (0)

Change History (3)

comment:1 Changed 3 years ago by anonymous

root@OpenWrt:/# cat /proc/mtd
dev: size erasesize name
mtd0: 00040000 00010000 "boot"
mtd1: 003b0000 00010000 "firmware"
mtd2: 000008f0 000008f0 "loader"
mtd3: 0010baf4 00010000 "linux"
mtd4: 002a3c00 00010000 "rootfs"
mtd5: 00040000 00010000 "rootfs_data"
mtd6: 00010000 00010000 "nvram"

comment:2 Changed 3 years ago by Zajec

Your report without a full boot log is - pardon - useless ;)

comment:3 Changed 3 years ago by nbd

  • Resolution set to too_vague
  • Status changed from new to closed

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.