Lew Wolfgang wrote:

On 12/16/2014 09:06 AM, Anton Aylward wrote:

...

...

Anyone know why a tar archive would fail when using a thumb drive?

I have a 250gig thumb drive that I'm trying to back up my home directory to and I get this error

/home/ruben/images/uragay_coin/IMG_1882.CR2 /home/ruben/images/uragay_coin/IMG_1937.CR2 /home/ruben/images/uragay_coin/uraguay_1969_new.jpg /home/ruben/images/uragay_coin/IMG_1830.JPG tar: /home/ruben/tape/workstation_12_15_2014.tar: Wrote only 4095 of 10240 bytes tar: Error is not recoverable: exiting now While 250G is impressive for a thumb drive, there are a couple of

On 12/16/2014 10:16 AM, Ruben Safir wrote: things I'd check.

1. Is it full?

I think the reason for that is obvious

2. What file system is it using?

Perhaps there is a limitation in file size with the FS, or the parameters used to create the FS.

I realise that larger thumb drives and SD cards are supposed to use exFAT which is supposed to support large files, but if I'm using a thumb drive for Linux backup I usually mkfs it to a linux file system.

Interesting timing. I ordered a 256-GB PNY thumb-drive from Amazon just last Saturday. It may be delivered later today.

Yes, I normally blow away the existing Windows filesystem on thumbs unless interchangability with Windows is a requirement. This hasn't been a requirement for years! I prefer XFS, and will try this on the new thumb, hopefully this evening.

Ruben: were there any other errors? Was this a media read error? Write? Checking /var/log/messages should tell. If not a media error and the thumb isn't full, could this be a tar bug?

It could perhaps be construed as a missing tar feature, i.e. when writing to a media with limited filesize, write multiple tar volumes. -- Per Jessen, Zürich (7.1°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Tue, Dec 16, 2014 at 09:45:05AM -0800, Lew Wolfgang wrote:

On 12/16/2014 09:06 AM, Anton Aylward wrote:

...

On 12/16/2014 10:16 AM, Ruben Safir wrote:

...

Anyone know why a tar archive would fail when using a thumb drive?

I have a 250gig thumb drive that I'm trying to back up my home directory to and I get this error

/home/ruben/images/uragay_coin/IMG_1882.CR2 /home/ruben/images/uragay_coin/IMG_1937.CR2 /home/ruben/images/uragay_coin/uraguay_1969_new.jpg /home/ruben/images/uragay_coin/IMG_1830.JPG tar: /home/ruben/tape/workstation_12_15_2014.tar: Wrote only 4095 of 10240 bytes tar: Error is not recoverable: exiting now While 250G is impressive for a thumb drive, there are a couple of things I'd check.

1. Is it full?

I think the reason for that is obvious

2. What file system is it using?

Perhaps there is a limitation in file size with the FS, or the parameters used to create the FS.

I realise that larger thumb drives and SD cards are supposed to use exFAT which is supposed to support large files, but if I'm using a thumb drive for Linux backup I usually mkfs it to a linux file system.

Interesting timing. I ordered a 256-GB PNY thumb-drive from Amazon just last Saturday. It may be delivered later today.

Yes, I normally blow away the existing Windows filesystem on thumbs unless interchangability with Windows is a requirement. This hasn't been a requirement for years! I prefer XFS, and will try this on the new thumb, hopefully this evening.

Ruben: were there any other errors? Was this a media read error? Write? Checking /var/log/messages should tell. If not a media error and the thumb isn't full, could this be a tar bug?

BTW, is anything being done to guard against "Bad USB" threats in Linux?

That is the only error. I did try to compress the tarball but it was too large for the compression, both bz and zip. I thought , though, that bz was not a size limited. Ruben

Regards, Lew

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www2.mrbrklyn.com/resources - Unpublished Archive http://www.coinhangout.com - coins! http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and and extermination camps, but incompatible with living as a free human being. -RI Safir 2013 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

В Tue, 16 Dec 2014 12:55:56 -0500 Greg Freemyer пишет:

...

BTW, is anything being done to guard against "Bad USB" threats in Linux?

Windows runs auto scripts found on the thumb when the thumb is inserted.

As far as I know Linux doesn't do that.

"Bad USB" is not about autorunning scripts. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Tue, Dec 16, 2014 at 1:17 PM, Lew Wolfgang wrote:

On 12/16/2014 09:55 AM, Greg Freemyer wrote:

...

And for Lew:

...

...

BTW, is anything being done to guard against "Bad USB" threats in

Linux?

Windows runs auto scripts found on the thumb when the thumb is inserted.

As far as I know Linux doesn't do that. So for a linux box to be infected by a thumb you would have to actively run the malicious app. Thus a linux obx is inherently far safer to look at thumb drives with than a Windows box.

Basically Windows ease of use features is one of the things that creates vulnerabilities for malicious apps to leverage.

Hi Greg,

I'm not sure autorun is the issue. BadUSB can make a RAM thumb drive appear as if it's a keyboard. Once the OS (Linux included) "mounts" the faux keyboard, BadUSB could start to type things, maybe in the context of the logged-in user? BadUSB could also hide boot code that would be totally transparent to the OS, and could maybe install a pre-boot loader that would install malware, then continue to the regularly scheduled boot? It might even be able to install malware into your mobo BIOS to give you a really persistent and undetectable infection. The list goes on. BadUSB is, really,,, bad. Some wags even think that state actors have been using this for years.

Regards, Lew

Sorry I missed that "BadUSB" was a specific form of maliciousness. I was thinking of generic bad USB drives with have malware on them that autorun from a script. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Tue, Dec 16, 2014 at 07:52:27PM -0800, Lew Wolfgang wrote:

On 12/16/2014 07:16 AM, Ruben Safir wrote:

...

Anyone know why a tar archive would fail when using a thumb drive?

I have a 250gig thumb drive that I'm trying to back up my home directory to and I get this error

/home/ruben/images/uragay_coin/IMG_1882.CR2 /home/ruben/images/uragay_coin/IMG_1937.CR2 /home/ruben/images/uragay_coin/uraguay_1969_new.jpg /home/ruben/images/uragay_coin/IMG_1830.JPG tar: /home/ruben/tape/workstation_12_15_2014.tar: Wrote only 4095 of 10240 bytes tar: Error is not recoverable: exiting now

I was able to recreate this tar error, the filesystem was just full. The kind of media and the type of filesystem is irrelevant, as expected. My error:

tar: /mnt/test.tar: Wrote only 6144 of 10240 bytes tar: Error is not recoverable: exiting now

and the df -h:

/dev/sdi1 239G 239G 20K 100% /mnt

Ruben, did you mount your thumb drive in your home directory? And did you then tar your home directory? If so, you may have recursively filled up your thumb drive. Try mounting the drive someplace like /mnt outside of the directory you're backing up.

Thaks Lew I did check to see if it was full, but it isn't. Obviously, however, it seems to be having trouble creating a file, It is fat so maybe that is the trouble. I'm gonna move everything off it and then try it with a GNU filesystem and see what happens. Yes, I did mount it in the home directory. That was weird and worth another discussion. This device was weird is a couple of ways. First, it will only mount as a whole disk, like a cdrom mount /dev/sdf no number Secondly, it wouldn't initially mount with RW access only RX I finally made an entry in fstab to force it to allow for execute on the mount point. There was problably a means to do with the mount comand, but I couldn't figure out the man page. I have no idea what happened with umask. I'm getting old Lew. Ruben

Regards, Lew

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www2.mrbrklyn.com/resources - Unpublished Archive http://www.coinhangout.com - coins! http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and and extermination camps, but incompatible with living as a free human being. -RI Safir 2013 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

check this out cfdisk Disk: /dev/sdf Size: 238.4 GiB, 255999344640 bytes, 499998720 sectors Label: dos, identifier: 0x6f20736b Device Boot Start End Sectors Size Id Type

...

Free space 2048 168689521 168687474 80.4G /dev/sdf1 ? 778135908 1919645538 1141509631 544.3G 72 unknown /dev/sdf2 ? 168689522 2104717761 1936028240 923.2G 65 Novell Netware 38 /dev/sdf3 ? 1869881465 3805909656 1936028192 923.2G 79 unknown /dev/sdf4 ? 2885681152 2885736650 55499 27.1M d unknown

when you tried to mount /dev/sdf1 though, it objected that there was no such device. [ruben@workstation ~]$ dmesg|grep sdf [ 590.801595] sd 5:0:0:0: [sdf] 499998720 512-byte logical blocks: (255 GB/238 GiB) [ 590.801963] sd 5:0:0:0: [sdf] Write Protect is off [ 590.801967] sd 5:0:0:0: [sdf] Mode Sense: 23 00 00 00 [ 590.802340] sd 5:0:0:0: [sdf] Write cache: disabled, read cache: disabled, doesn't support DPO or FUA [ 590.806007] sdf: [ 590.808091] sd 5:0:0:0: [sdf] Attached SCSI removable disk [ 701.985394] FAT-fs (sdf): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. [ 964.484631] FAT-fs (sdf): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. [ 1257.324390] FAT-fs (sdf): Unrecognized mount option "unhid" or missing value [ 1317.868396] FAT-fs (sdf): Unrecognized mount option "unhide" or missing value [ 1356.259403] FAT-fs (sdf): Unrecognized mount option "unhide" or missing value [ 1366.428825] FAT-fs (sdf): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. [ 2138.113055] FAT-fs (sdf): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. [ruben@workstation ~]$ Here is the thing. I was reluctant to blow away the file system on this thumb drive because it is expensive and I didn't want to brick it.,, which can happen with these UEFI complient devices. On Wed, Dec 17, 2014 at 04:08:42PM +0100, jdd wrote:

Le 17/12/2014 15:56, Ruben Safir a écrit :

...

it will only mount as a whole disk, like a cdrom

mount /dev/sdf

no number

possible but not usual, better have at least one partition

...

Secondly, it wouldn't initially mount with RW access only RX

I have this often, unfriendly but not fatal

...

I finally made an entry in fstab to force it to allow for execute on the mount point. There was problably a means to do with the mount comand, but I couldn't figure out the man page.

I'm wondering if this device, big as it is, was even prepared or not? It's not normal to have a large disk formatted but not partitionned.

Better partition it first, even with several partitions (at will) Notice also that plain FAT file system have a limited number of files *in the root of the disk*. Don't know if it's always the case for newer brands, but it's enough to copy the files to any other folder than root to go as much as you want

jdd

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www2.mrbrklyn.com/resources - Unpublished Archive http://www.coinhangout.com - coins! http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and and extermination camps, but incompatible with living as a free human being. -RI Safir 2013 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Wed, Dec 17, 2014 at 04:42:11PM +0100, jdd wrote:

Le 17/12/2014 16:38, Ruben Safir a écrit :

...

check this out

cfdisk

Disk: /dev/sdf Size: 238.4 GiB, 255999344640 bytes, 499998720 sectors Label: dos, identifier: 0x6f20736b

Device Boot Start End Sectors Size Id Type

...

...

Free space 2048 168689521 168687474 80.4G /dev/sdf1 ? 778135908 1919645538 1141509631 544.3G 72 unknown /dev/sdf2 ? 168689522 2104717761 1936028240 923.2G 65 Novell Netware 38 /dev/sdf3 ? 1869881465 3805909656 1936028192 923.2G 79 unknown /dev/sdf4 ? 2885681152 2885736650 55499 27.1M d unknown

obviously damaged partition table (total partitions size is more than the disk size), remove all this and build it again

good point df understands it though [ruben@workstation ~]$ df -h Filesystem Size Used Avail Use% /home /dev/sdf 239G 118G 121G 50% /home/ruben/tape ruben@www.mrbrklyn.com:/usr/local/apache/htdocs/ 430G 282G 148G 66% /home/ruben/webserver

yast can create the file system at the same time

jdd

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www2.mrbrklyn.com/resources - Unpublished Archive http://www.coinhangout.com - coins! http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and and extermination camps, but incompatible with living as a free human being. -RI Safir 2013 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 12/17/2014 10:42 AM, Anton Aylward wrote:

That's why I referred you guys to extFAT.

I prefer ext4. ;-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 12/17/2014 11:28 AM, Anton Aylward wrote:

All those are exFAT.

Yes, I'd prefer it if they used ext4, but they don't.

I guess you missed my attempt at humour with this. In the comment I replied to, you said extFAT, not exFAT. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Le 17/12/2014 16:42, Anton Aylward a écrit :

On 12/17/2014 10:08 AM, jdd wrote:

...

Notice also that plain FAT file system have a limited number of files *in the root of the disk*. Don't know if it's always the case for newer brands, but it's enough to copy the files to any other folder than root to go as much as you want

FAT also has a limit on file sizes That's why I referred you guys to extFAT.

yes, but I didn't know if the file number limit was still in value. I seems not to be, I found: "The root folder on a FAT32 drive is now an ordinary cluster chain, so it can be located anywhere on the volume. For this reason, FAT32 does not restrict the number of entries in the root folder". but the ruben disk was obviously damaged - not surprising is write direct to /dev/sdx was done. I don't really know what the filesystem do when writing to the full device (ie no partition), but may be the first sector is not used, at best. jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 2014-12-17 16:08, jdd wrote:

Notice also that plain FAT file system have a limited number of files *in the root of the disk*. Don't know if it's always the case for newer brands, but it's enough to copy the files to any other folder than root to go as much as you want

It is a FAT limitation, it does not depend on brand, and not much size: the root directory has always a limited number of entries, relatively few. Subdirectories are basically unlimited, but reading them becomes slower and slower as the number of entries increases (the directory list itself becomes fragmented). -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)

On Wed, Dec 17, 2014 at 12:15:40PM -0500, Ken wrote:

On December 16, 2014 10:52:27 PM EST, Lew Wolfgang wrote:

...

...

Anyone know why a tar archive would fail when using a thumb drive?

I have a 250gig thumb drive that I'm trying to back up my home

On 12/16/2014 07:16 AM, Ruben Safir wrote: directory

...

to and I get this error

/home/ruben/images/uragay_coin/IMG_1882.CR2 /home/ruben/images/uragay_coin/IMG_1937.CR2 /home/ruben/images/uragay_coin/uraguay_1969_new.jpg /home/ruben/images/uragay_coin/IMG_1830.JPG tar: /home/ruben/tape/workstation_12_15_2014.tar: Wrote only 4095 of 10240 bytes tar: Error is not recoverable: exiting now

I was able to recreate this tar error, the filesystem was just full. The kind of media and the type of filesystem is irrelevant, as expected. My error:

tar: /mnt/test.tar: Wrote only 6144 of 10240 bytes tar: Error is not recoverable: exiting now

and the df -h:

/dev/sdi1 239G 239G 20K 100% /mnt

Ruben, did you mount your thumb drive in your home directory? And did you then tar your home directory? If so, you may have recursively filled up your thumb drive. Try mounting the drive someplace like /mnt outside of the directory you're backing up.

Or use the raw device like you would tape. Just use /dev/sdi as the destination. Tar does not require a file system.

I thought of that but then I thought I would destroy the entire FS on the device like you would with a dd command. I have other data on there as well Ruben

Ken -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www2.mrbrklyn.com/resources - Unpublished Archive http://www.coinhangout.com - coins! http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and and extermination camps, but incompatible with living as a free human being. -RI Safir 2013 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org