Re: [vox-tech] Help with USB Hard drive

2009-02-20 Thread Bill Broadley
chris wrote:
> On Fri, 2009-02-20 at 17:53 -0800, Bill Broadley wrote:
> 
>> Er, there is recovery, it's called, er, umm, chkdsk or something?u are I 
>> think
>> there's a fsck.vfat as well.
> 
>chkdsk is only good for saving readable text, if it is .exe you want
> back then you are mostly screwed. 

Really, I don't recall such restrictions, but it's been a very long time so
I'll just blame my memory.  fsck.vfat mentions fixing quite a few things.

> journal roll back will only lose that
> data recently added, instead of the entire fs.

As mentioned, that's the theory, if everything is perfect.  Alas the real
world means that block numbers, contents, messages, drivers, etc during an
issue (like a power supply failure, brownout) or even just a driver bug.  It
could even be something as subtle as a vibration.

> So basicly, save oven and
> make plenty copies.

Sure, rsync, backups, version control etc.  The way I do things like this is:
* Email keep it on server, backup the server (backuppc in my cse)
* source code remote subversion server (again backed up by backuppc)
* Important non-source code related files rsync

The rest... when it dies I consider it house cleaning.
> 
> 
> 
> 
> 
___
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech


Re: [vox-tech] Help with USB Hard drive

2009-02-20 Thread chris
On Fri, 2009-02-20 at 17:53 -0800, Bill Broadley wrote:

> Er, there is recovery, it's called, er, umm, chkdsk or something?u are I think
> there's a fsck.vfat as well.

   chkdsk is only good for saving readable text, if it is .exe you want
back then you are mostly screwed. journal roll back will only lose that
data recently added, instead of the entire fs. So basicly, save oven and
make plenty copies.





-- 
chris 
http://digitalatoll.flnet.org/
___
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech


Re: [vox-tech] Help with USB Hard drive

2009-02-20 Thread Bill Broadley
Scott Miller wrote:
> Hey yeah FAT32 is not journaling either, so if there is every a power
> blip or cut of connection there is zero recovery from the file system
> (if that is a concern).

Er, there is recovery, it's called, er, umm, chkdsk or something?  I think
there's a fsck.vfat as well.

Speaking of which another of my pet peeves/rants.  Journals rely on perfectly
reliable hardware, drivers, cables, and software.  Unfortunately the real
world isn't so kind.  So the reality is that the periodic fsck gives a much
stronger statement of a file systems integrity than a simple journal unroll.

Based on my experience the quality of the file system and hardware is hugely
more important than the existence or lack of journaling.  In fact if anything
I've seen more issues with xfs and reiser than I have with ext2 or ext3
(percentage wise, not in absolute terms).

I'm not against journals and run ext3 most commonly, but journals are mostly
about quick boot/mount times, not safer, and actually they tend to less safe.
___
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech


Re: [vox-tech] Help with USB Hard drive

2009-02-20 Thread Scott Miller
Hey yeah FAT32 is not journaling either, so if there is every a power
blip or cut of connection there is zero recovery from the file system
(if that is a concern).

This wikipedia page is one of my favorites, btw:

http://en.wikipedia.org/wiki/Comparison_of_file_systems


On Fri, Feb 20, 2009 at 11:01, ALLO (Alfredo Lopez De Leon)
 wrote:
> Hi ken and Matthew,
>
> Awesome info!  I'll give it a try :-)
>
> Ken: does this answer your question?
>
> Disk /dev/sdf: 1000.2 GB, 1000204886016 bytes
> 255 heads, 63 sectors/track, 121601 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
>   Device Boot  Start End  Blocks   Id  System
> /dev/sdf1   1  121601   976760001b  W95 FAT32
>
> By the way I decided to use FAT32 so I can move the drive between several 
> machines. But.., I may decide to get another one ($150.00 at Fry's final 
> price) and do the "/dev/disk/by-id/" but with an ext3 partition which 
> will be much more efficient.
>
> Thanks!!!
> Alfredo
>
> -Original Message-
> From: vox-tech-boun...@lists.lugod.org 
> [mailto:vox-tech-boun...@lists.lugod.org] On Behalf Of Chanoch (Ken) Bloom
> Sent: Friday, February 20, 2009 10:03 AM
> To: lugod's technical discussion forum
> Subject: Re: [vox-tech] Help with USB Hard drive
>
>
> That's an assumption the operating system makes because most USB drives are 
> thumb drives and the like, single-user disks that come and go. You can change 
> that, though.
>
> Create a rule to identify the device uniquely in udev and to assign it a 
> permenant device node (I can't tell you exactly how to do this, it will 
> depend on being able to find something like a serial number that udev can use 
> to identify it.), then add that device node to /etc/fstab, with appropriate 
> mount options.
>
> Just out of curiousity, what's the block size (the size occupied by a 1 byte 
> file) on a 1 TB fat32 drive?
>
> --Ken
>
> --
> Ken (Chanoch) Bloom. PhD candidate. Linguistic Cognition Laboratory.
> Department of Computer Science. Illinois Institute of Technology.
> http://www.iit.edu/~kbloom1/
> ___
> vox-tech mailing list
> vox-tech@lists.lugod.org
> http://lists.lugod.org/mailman/listinfo/vox-tech
>
___
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech


Re: [vox-tech] keyboard problems after aptitude upgrade [fixed]

2009-02-20 Thread Dylan Beaudette
On Wednesday 11 February 2009, Ken Bloom wrote:
> Can you tell us what distribution you're running, and tell us what got
> upgraded in /var/log/aptitude?
>
> --Ken

Seems like an incomplete upgrade of KDM was to blame. This was fixed by 
issuing:

sudo aptitude install kdm
[fixing some dependencies]

everything was fine after the upgrade.

Thanks for the ideas,

Dylan

-- 
Dylan Beaudette
Soil Resource Laboratory
http://casoilresource.lawr.ucdavis.edu/
University of California at Davis
530.754.7341
___
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech


[vox-tech] mysterious messages

2009-02-20 Thread Dylan Beaudette
Hi,

I have seen these messages recently (dmesg):


[1434580.283311] INFO: task vol_id:904 blocked for more than 120 seconds.
[1434580.283321] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
[1434580.283325] vol_idD 85e7f2c5 0   904  1
[1434580.283331]e55db0c0 0086 e5646800 85e7f2c5 00036dde e55db24c 
c2817fa0  
[1434580.283356]e10ee24c 11162f58 91ed  11162f58 e10ee24c 
11162f58 c2802678 
[1434580.283382]c2817fa0 0245d000 c2802678 c015800f c02b8458 ddbede50 
ddbede50 c01568bd 
[1434580.283410] Call Trace:
[1434580.283476]  [] sync_page_killable+0x0/0x2a
[1434580.283488]  [] io_schedule+0x49/0x80
[1434580.283500]  [] sync_page+0x33/0x36
[1434580.283505]  [] sync_page_killable+0x5/0x2a
[1434580.283510]  [] __wait_on_bit_lock+0x2a/0x52
[1434580.283523]  [] __lock_page_killable+0x51/0x57
[1434580.283538]  [] wake_bit_function+0x0/0x3c
[1434580.283553]  [] generic_file_aio_read+0x331/0x4da
[1434580.283611]  [] do_sync_read+0xbf/0xfe
[1434580.283666]  [] autoremove_wake_function+0x0/0x2d
[1434580.283681]  [] vma_merge+0xd3/0x142
[1434580.283711]  [] security_file_permission+0xc/0xd
[1434580.283725]  [] do_sync_read+0x0/0xfe
[1434580.283732]  [] vfs_read+0x81/0x11e
[1434580.283747]  [] sys_read+0x3c/0x63
[1434580.283764]  [] sysenter_past_esp+0x78/0xb1
[1434580.283809]  ===


Does this mean anything to anyone on the list?

Thanks,

Dylan

-- 
Dylan Beaudette
Soil Resource Laboratory
http://casoilresource.lawr.ucdavis.edu/
University of California at Davis
530.754.7341
___
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech


Re: [vox-tech] Help with USB Hard drive

2009-02-20 Thread ALLO (Alfredo Lopez De Leon)
Hi ken and Matthew,

Awesome info!  I'll give it a try :-)  

Ken: does this answer your question?

Disk /dev/sdf: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot  Start End  Blocks   Id  System
/dev/sdf1   1  121601   976760001b  W95 FAT32

By the way I decided to use FAT32 so I can move the drive between several 
machines. But.., I may decide to get another one ($150.00 at Fry's final price) 
and do the "/dev/disk/by-id/" but with an ext3 partition which will be much 
more efficient.

Thanks!!!
Alfredo

-Original Message-
From: vox-tech-boun...@lists.lugod.org 
[mailto:vox-tech-boun...@lists.lugod.org] On Behalf Of Chanoch (Ken) Bloom
Sent: Friday, February 20, 2009 10:03 AM
To: lugod's technical discussion forum
Subject: Re: [vox-tech] Help with USB Hard drive


That's an assumption the operating system makes because most USB drives are 
thumb drives and the like, single-user disks that come and go. You can change 
that, though.

Create a rule to identify the device uniquely in udev and to assign it a 
permenant device node (I can't tell you exactly how to do this, it will depend 
on being able to find something like a serial number that udev can use to 
identify it.), then add that device node to /etc/fstab, with appropriate mount 
options.

Just out of curiousity, what's the block size (the size occupied by a 1 byte 
file) on a 1 TB fat32 drive?

--Ken

--
Ken (Chanoch) Bloom. PhD candidate. Linguistic Cognition Laboratory.
Department of Computer Science. Illinois Institute of Technology.
http://www.iit.edu/~kbloom1/
___
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech


Re: [vox-tech] Help with USB Hard drive

2009-02-20 Thread Matthew Holland
To add to what Ken said, if you're using udev, you should be able to get a
stable device identifier by looking in /dev/disk/by-id.  Usually the name
there is informative enough to just figure it directly.  Recent Fedora and
Ubuntu distros have this facility.  You can then use /dev/disk/by-id/ in
/etc/fstab as Ken suggested.
Matt

On Fri, Feb 20, 2009 at 11:03 AM, Chanoch (Ken) Bloom wrote:

> On Fri, 2009-02-20 at 11:49 -0500, ALLO (Alfredo Lopez De Leon) wrote:
> > Hi,
> > Thank you very much for all your answers.  After testing some of your
> > suggestions I "discovered" that It is after all a USB drive and as
> > root I have to umount it before logging out so the other users can
> > mount it and use it...
> >
> > Too bad USB drives do not behave like "real attached drives".  Well.
> > Like the Rolling Stones would say: You can't always get what you want.
> >
> > Have a nice one!
> >
> > Alfredo
>
> That's an assumption the operating system makes because most USB drives
> are thumb drives and the like, single-user disks that come and go. You
> can change that, though.
>
> Create a rule to identify the device uniquely in udev and to assign it a
> permenant device node (I can't tell you exactly how to do this, it will
> depend on being able to find something like a serial number that udev
> can use to identify it.), then add that device node to /etc/fstab, with
> appropriate mount options.
>
> Just out of curiousity, what's the block size (the size occupied by a 1
> byte file) on a 1 TB fat32 drive?
>
> --Ken
>
> --
> Ken (Chanoch) Bloom. PhD candidate. Linguistic Cognition Laboratory.
> Department of Computer Science. Illinois Institute of Technology.
> http://www.iit.edu/~kbloom1/
>
>
> ___
> vox-tech mailing list
> vox-tech@lists.lugod.org
> http://lists.lugod.org/mailman/listinfo/vox-tech
>
>
___
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech


Re: [vox-tech] Help with USB Hard drive

2009-02-20 Thread Chanoch (Ken) Bloom
On Fri, 2009-02-20 at 11:49 -0500, ALLO (Alfredo Lopez De Leon) wrote:
> Hi,
> Thank you very much for all your answers.  After testing some of your
> suggestions I "discovered" that It is after all a USB drive and as
> root I have to umount it before logging out so the other users can
> mount it and use it...
> 
> Too bad USB drives do not behave like "real attached drives".  Well.
> Like the Rolling Stones would say: You can't always get what you want.
> 
> Have a nice one!
> 
> Alfredo

That's an assumption the operating system makes because most USB drives
are thumb drives and the like, single-user disks that come and go. You
can change that, though.

Create a rule to identify the device uniquely in udev and to assign it a
permenant device node (I can't tell you exactly how to do this, it will
depend on being able to find something like a serial number that udev
can use to identify it.), then add that device node to /etc/fstab, with
appropriate mount options.

Just out of curiousity, what's the block size (the size occupied by a 1
byte file) on a 1 TB fat32 drive?

--Ken

-- 
Ken (Chanoch) Bloom. PhD candidate. Linguistic Cognition Laboratory.
Department of Computer Science. Illinois Institute of Technology.
http://www.iit.edu/~kbloom1/



signature.asc
Description: This is a digitally signed message part
___
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech


Re: [vox-tech] Help with USB Hard drive

2009-02-20 Thread ALLO (Alfredo Lopez De Leon)
Hi,
Thank you very much for all your answers.  After testing some of your 
suggestions I "discovered" that It is after all a USB drive and as root I have 
to umount it before logging out so the other users can mount it and use it...

Too bad USB drives do not behave like "real attached drives".  Well. Like the 
Rolling Stones would say: You can't always get what you want.

Have a nice one!

Alfredo


-Original Message-
From: vox-tech-boun...@lists.lugod.org 
[mailto:vox-tech-boun...@lists.lugod.org] On Behalf Of Jeffrey Nonken
Sent: Thursday, February 19, 2009 7:59 PM
To: lugod's technical discussion forum
Subject: Re: [vox-tech] Help with USB Hard drive

Did you make sure of the permissions on the mounting point?

On Feb 19, 2009, at 2:31 PM, ALLO (Alfredo Lopez De Leon) wrote:

> Hi,
> I have a brand new 1TB USB hard drive formatted by fdisk to FAT32.
> My system can see it mount it and umount it.
> However, no matter what I do I cannot change the permissions or the  
> ownership nothing!
> The root can write but nobody else can.
> I want this drive to be totally accessible to all the users of the  
> machine (actually a server).
>
> Is there a way to do this?
___
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech
___
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech