"Michael S. Zick":
> So far, the winner is (other than physical volume) punched paper;
> Either cards or tape on media that was intended for archival storage.
> Most of that which I have is approaching 50 years, and those little
> holes are still there. It is nice to be able to see each bit. ;-)
Hi!
What about the amount of bytes written? We are talking about 100K and 1M
of cycles - on the same cell or any?
My task is not fundamental development, but making reliable equipment,
utilizing flash memory. And yes I need life time as long as possible. Also
I have a lot of RAM. One of friends my
On Wed November 30 2011, Klaus Knopper wrote:
> Also, flash media ages. Manufacturers only guarantee cells to hold the
> information up to 10 years, so, flash is probably not good for long term
> storage. Well... Similar problem for magnetical or optical storage,
> which make it up to 50 years only
Hello Junjiro & list,
On Wed, Nov 30, 2011 at 08:28:39PM +0900, sf...@users.sourceforge.net wrote:
>
> Klaus Knopper:
> > Various approaches, from just creating and deleting files over the file
> :::
>
> OK.
>
>
> > Like in
> > dd if=/dev/urandom of=/dev/sdb oflag=direct,sync bs=131072
>
Klaus Knopper:
> Various approaches, from just creating and deleting files over the file
:::
OK.
> Like in
> dd if=/dev/urandom of=/dev/sdb oflag=direct,sync bs=131072
> ?
Yes, oflag=direct is what I meant.
Even if you applied direct-io, you could not see the write limit on your
flash,
Hi Junjiro,
On Wed, Nov 30, 2011 at 11:52:03AM +0900, sf...@users.sourceforge.net wrote:
>
> Hello Kalus,
>
> Klaus Knopper:
> > From my own experience, I was not able to kill an usual USB flash disk
> > or SD card by "excessive" writes yet. I tried hard, really, even with
> > the mount -o sync
Hello Kalus,
Klaus Knopper:
> From my own experience, I was not able to kill an usual USB flash disk
> or SD card by "excessive" writes yet. I tried hard, really, even with
> the mount -o sync option. The german c't magazine has also run write
> tests over a year with millions of writes, and was
>
> On Nov 29, 2011, at 10:45 AM, tovis wrote:
>
> tovis:
>
> I am interested in minimizing writes to a boot flash drive as well. I
have a Seagate Dockstar (arm5, 128 MB RAM) that boots Debian wheezy from
a usb flash drive. It runs rtorrent, sabnzbd, and rsync. These programs
operate on files that
On Nov 29, 2011, at 10:45 AM, tovis wrote:
tovis:
I am interested in minimizing writes to a boot flash drive as well. I have a
Seagate Dockstar (arm5, 128 MB RAM) that boots Debian wheezy from a usb flash
drive. It runs rtorrent, sabnzbd, and rsync. These programs operate on files
that are on
On Tue November 29 2011, tovis wrote:
> > On Tue November 29 2011, Klaus Knopper wrote:
> >> -Klaus Knopper
> >> PS: Now this got somewhat lengthy, sorry. I may reuse this explanation for
> >> an article later.
> >>
> I haven't seen this mail!?
>
http://sourceforge.net/mailarchive/message.php?msg
> On Tue November 29 2011, Klaus Knopper wrote:
>> -Klaus Knopper
>> PS: Now this got somewhat lengthy, sorry. I may reuse this explanation for
>> an article later.
>>
I haven't seen this mail!?
> Pay close attention to things being done by the builders of embedded
systems. Reducing the number of
"tovis":
> Thanks a lot! Why I'm do not seen it's in the documentation?
I am afraid you just didn't read Documentation/ABI/testing/sysfs-aufs.
> That's all. I think it is simple enough. Juggling with mounts? Why? Why
> are you (with Mike) suggest me do not use aufs? Even is it included to
Beca
Hi!
> J. R. Okajima
>
> I guess what you want is /sys/fs/aufs/si_*/br[0-9]*.
>
Thanks a lot! Why I'm do not seen it's in the documentation?
>> One more question, is it possible to change/modify a built up branch -
>> making rw from ro of the lower part?
> J. R. Okajima
>
> Try "mount -o remount,m
On Tue November 29 2011, Klaus Knopper wrote:
> -Klaus Knopper
> PS: Now this got somewhat lengthy, sorry. I may reuse this explanation for
> an article later.
>
It reads well just as it is.
But if you really feel the urge to write a longer article... ;-)
Linux specific, any degree of leveling
Hello tovis & list,
On Mon, Nov 28, 2011 at 08:48:15PM +0100, tovis wrote:
> J. R. Okajima
> > Unfortunately I don't understand what you wrote and what you want to do.
> >
> Short way, I want minimize writes to USB which used as a hard disk, in an
> embedded like equipment, move the life time up t
"tovis":
> Other question (may be suggestion) is it possible to now that the
> underlaying branch is read-only? The mount and cat /proc/mounts also sad
> that mount is rw!? - it is really confusing (I have lost many hours and
> hair).
I guess what you want is /sys/fs/aufs/si_*/br[0-9]*.
J. R. Okajima
> Unfortunately I don't understand what you wrote and what you want to do.
>
Short way, I want minimize writes to USB which used as a hard disk, in an
embedded like equipment, move the life time up to year or more.
To reach this I have to use aufs, to unify some directories and files
>
> "tovis":
>> I have tried:
>> #mount -t aufs -o br:/mnt/var:/var=wr none /var
>
> I am afraid you are confusing "=rw" and "=wr".
>
>
> J. R. Okajima
>
>
Hi! You right! My fault!
It's embarassing! It is not the first time and I'm afraid not the last one :(
Also, now I have set my init script with
"tovis":
> I have tried:
> #mount -t aufs -o br:/mnt/var:/var=wr none /var
I am afraid you are confusing "=rw" and "=wr".
J. R. Okajima
--
All the data continuously generated in your IT infrastructure
contains a defin
>
> "tovis":
>> Each directories /mnt/var and /var are writable, now for sure, but if I
>> append something to /var/testing/zebulon.txt immediately create an
>> updated
>> version for /mnt/var/testing/zebulon.txt and after reboot changes are
>> lost
>> in /var/testing/zebulon.txt
>> What could be w
"tovis":
> Each directories /mnt/var and /var are writable, now for sure, but if I
> append something to /var/testing/zebulon.txt immediately create an updated
> version for /mnt/var/testing/zebulon.txt and after reboot changes are lost
> in /var/testing/zebulon.txt
> What could be wrong?
> Do I n
Hi everyone!
I'm still stuck on copy-up on Squeeze:(
For testing purposes I have created a file under a new directory
/var/testing/zebulon.txt. After fully booted Squeeze I have do my script
which was at start before all other thing in /etc/rcS.d
mount -t tmpfs none /mnt/var #create a writ
"tovis":
> This was only the first try. For now I'm trying to refine this option, for
> example put logs to the tmpfs but save crontabs to USB. I have deleted
For such purpose, I'd suggest you NOT to use aufs.
# mount /dev/your/USB /var
# mount -t tmpfs /var/log
should be enough (the initial logs
"J. R. Okajima"
>
> If you set RW to the lower branch, you can.
> But you wrote that you did copy all files to the upper branch. It means
> all modifications are made on tmpfs and you don't need aufs. As long as
> the file exists on the upper tmpfs, aufs will never touch the same named
> file on th
"tovis":
> It is possible that I was wrong informed! I'm trying to translate what
> friend sad about unionfs:
> Everything which is reside on tmpfs at start of the branching is modified
> only in tmpfs. Everything which is exist on tmpfs and USB also modified in
> tmpfs. Everything which is new to
"tovis":
> But something wrong :( At first I'm trying to edit my user's crontab,
> which exist only in /var/spool/cron/crontabs/"me" and does not exist on
> /mnt/var. After reboot my edits was lost :( Same with
> /var/lib/alsa/asound.state - also exist only on USB.
> What is wrong? Any ideas? Any
Hello everyone!
Still something wrong, what I have missed?
After some struggling, I have simply checked last modification time of
every files in the /var directory, and filtered the files which are
changed in a one-two day interval.
I have boot a RIP kernel through PXE and move every directory and
> Have you tried:
> mount --move /var /mnt/var
> at this point and skipping all of the following?
>
> See: man mount
>
> Mike
Hello Mike!
Thanks, not. It's in progress. For example crontabs need to be stay on USB
(for now with whole /var I always should reedit after every reboot).
Other question, h
Hello everyone!
Thanks for your valuable help and time!
I have achieved some progress.
I try to describe step-by-step - may be it could help for some one.
1. Make a directory /mnt/var
#mkdir /mnt/var
2. Copy (for now) whole /var (using mc) and make a tartbal:
#tar -czf /boot/aufs_var.tar.gz /
Ben Hutchings:
> I was hoping you would be able to identify the most important fixes,
> dealing with data loss and security bugs. This long list of changes
> appears to include cleanup and new features, which would not be
No, such changes are removed.
You may be able to see what I have removed i
On Mon, 2011-11-21 at 14:02 +0900, sf...@users.sourceforge.net wrote:
> (While I don't know this mail is delivered expectedly, I am sending to
> debian-live and debian-kernel ML too since Ben Hutchings requested me to
> do so. Note that aufs-users ML is members only and your reply may be
> rejected
(While I don't know this mail is delivered expectedly, I am sending to
debian-live and debian-kernel ML too since Ben Hutchings requested me to
do so. Note that aufs-users ML is members only and your reply may be
rejected.)
Hello Ben,
Ben Hutchings:
> If there are important bug fixes that aren'
On Mon, 2011-11-21 at 09:18 +0900, sf...@users.sourceforge.net wrote:
> Hello tovis,
>
> "tovis":
> > I have read man, aufs html documentation but I have still do not
> > understand how to construct the command for making ro /var to be a unified
> > with /tmp/var wr so in result every files in /va
> AuFS cannot union mount its own mountpoint, so I don't think it's
> possible. At least I couldn't get such setups to work.
> The only way to make it work is to copy all the files from /var to
> /var.real and perform the union mount early in the boot process before
> anything is written to /var,
"tovis":
> file system, which includes it. Suggestion about unionfs (I have got from
> hup.hu) is working if I copy some part of /var to place for rw area for
> /var. The translation:
> You should make a script which is should run first at the start
> (rcS.d/S00unionfs), and it should do the next:
Hello tovis,
"tovis":
> I have read man, aufs html documentation but I have still do not
> understand how to construct the command for making ro /var to be a unified
> with /tmp/var wr so in result every files in /var are seen by system but
> writes to /var goes to ramdisk/tmpfs ...
Generally yo
oops! I was send to user! I'm very sorry :(
>> unionfs-fuse ... yes it is exist in Debian (as backport).
>> Why two separate "-o" option group?
> one goes to unionfs-fuse and the other to FUSE itself.
>
>> The branch(?) is "/tmp/var"=RW:"/var"=RO "/var" mean that /tmp/var (which
>> is created at /t
> unionfs-fuse ... yes it is exist in Debian (as backport).
> Why two separate "-o" option group?
one goes to unionfs-fuse and the other to FUSE itself.
> The branch(?) is "/tmp/var"=RW:"/var"=RO "/var" mean that /tmp/var (which
> is created at /tmp which is a tmpfs - ramdisk) as writable and it i
> Hi Tovis!
>
> I haven't figured out a way to do it using AuFS without moving /var,
> but AFAIK overlayfs does what you want. It's included in Ubuntu
> Oneiric kernel, but I'm not sure about Debian.
>
> I'm looking for a way to do it without overlayfs requirement myself,
> if you find one, please
Hi Tovis!
I haven't figured out a way to do it using AuFS without moving /var,
but AFAIK overlayfs does what you want. It's included in Ubuntu
Oneiric kernel, but I'm not sure about Debian.
I'm looking for a way to do it without overlayfs requirement myself,
if you find one, please let me know!
40 matches
Mail list logo
