"Downloads-1.(null)" file in ~/

benwiggy · 12-29-2012, 01:50 PM

I've just noticed two files that have appeared in the top level of my user domain:
Downloads-1.(null)
Downloads-2.(null)

They appear to be identical and contain data from some files I've downloaded. I can't find any webpages that describe them. I'm sure it'll be find to delete them, but I'm just curious about their purpose/origin. Obviously some sort of Safari temp file…

Anyone know anything about these?

DeltaMac · 12-29-2012, 02:30 PM

(null) extension, in my experience, is usually a corrupted file.
Do you also have a Downloads folder in your user folder? If the Downloads folder is not at that folder level, then you may simply have a couple of partial downloads, or just corrupted somehow.
If you can't open either one, with TextEdit, or some other text editor (Text Wrangler would be good to try, too), then the trash is a good next step for both files.
If there is NOT a Downloads folder in your user folder, then I suggest that you create one just to leave there. Maybe that will help whatever is causing those files to be created improperly.

benwiggy · 12-29-2012, 03:30 PM

Yes, I have a Downloads folder. The file contains data from an .eps file which I downloaded successfully; also it makes reference to the QuickTime 7 player, which I also downloaded (apparently) successfully recently.

I'll verify the disk. Thanks for the info.

EDIT: Disk appears fine, but Ooh, really interesting DU log from the Fusion Drive!

Code:

Verifying volume “Macintosh HD”
Checking storage systemChecking volume.
disk0s2: Scan for Volume Headers
disk1s2: Scan for Volume Headers
disk0s2: Scan for Disk Labels
disk1s2: Scan for Disk Labels
Logical Volume Group 0AC8C48A-824D-4627-87E3-E9E112253B07 spans 2 devices
disk0s2+disk1s2: Scan for Metadata Volume
Logical Volume Group has a 1609 MB Metadata Volume with double redundancy
Start scanning metadata for a valid checkpoint
Load and verify Segment Headers
Load and verify Checkpoint Payload
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Incorporate 53 newer non-checkpoint transactions
Load and verify Virtual Address Table
Load and verify Segment Usage Table
Load and verify Metadata Superblock
Load and verify Logical Volumes B-Trees
Logical Volume Group contains 1 Logical Volume
Load and verify 6FEC9974-46CB-4E5C-A393-BCFE062E2BA6
Load and verify 9762E938-B774-4938-AF07-B5DA34812251
Load and verify Freespace Summary
Load and verify Block Accounting
Load and verify Live Virtual Addresses
Newest transaction commit checkpoint is valid
Load and verify Segment Cleaning
The volume 0AC8C48A-824D-4627-87E3-E9E112253B07 appears to be OK.
Checking file systemPerforming live verification.
Checking Journaled HFS Plus volume.
Checking extents overflow file.
Checking catalog file.
Checking multi-linked files.
Checking catalog hierarchy.
Checking extended attributes file.
Checking volume bitmap.
Checking volume information.
The volume Macintosh HD appears to be OK.

DeltaMac · 12-29-2012, 03:47 PM

Have you looked at that DU log before, since you have the Fusion drive?
That log may be very normal for your configuration.

I wonder if those (null) files are detritus from the changeover from a "downloading" file, to a "downloaded" file, that the file system doesn't quite deal with properly. Do those files show the same date (more or less)? Could be some weirdness in your system that just needs a restart.

benwiggy · 12-29-2012, 03:52 PM

Oh yes: I'm sure it's a normal log for the hardware: I've just never seen it before.

I restart my Mac every morning: I'm sure it's just some random anomaly, I was just interested in its provenance.
The two files have identical data and are one minute apart in creation date.

DeltaMac · 12-29-2012, 06:28 PM

Well, it sounds like it was connected with downloads that were successful at the time - even though there was some glitch, even something small like a short power interruption on your router (or maybe on the ISPs end), interfering briefly with your download, not enough to error out - but just long enough to leave you with a small mysterious "gift"
If you have had normal downloads since that time, then just count it as a temporary wonder.
As I think about it - maybe it's some small bug in the Fusion drive - the algorithm may still need some tweaking in a future ML system update for a Fusion drive that may be not quite 100% for all operations.

12-29-2012, 01:50 PM	#1
benwiggy League Commissioner Join Date: Aug 2006 Posts: 5,039	"Downloads-1.(null)" file in ~/ I've just noticed two files that have appeared in the top level of my user domain: Downloads-1.(null) Downloads-2.(null) They appear to be identical and contain data from some files I've downloaded. I can't find any webpages that describe them. I'm sure it'll be find to delete them, but I'm just curious about their purpose/origin. Obviously some sort of Safari temp file… Anyone know anything about these?

Thread Tools
Show Printable Version Email this Page
Display Modes	Rate This Thread
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode	Rate This Thread:

12-29-2012, 02:30 PM	#2
DeltaMac League Commissioner Join Date: Jan 2002 Posts: 7,948	(null) extension, in my experience, is usually a corrupted file. Do you also have a Downloads folder in your user folder? If the Downloads folder is not at that folder level, then you may simply have a couple of partial downloads, or just corrupted somehow. If you can't open either one, with TextEdit, or some other text editor (Text Wrangler would be good to try, too), then the trash is a good next step for both files. If there is NOT a Downloads folder in your user folder, then I suggest that you create one just to leave there. Maybe that will help whatever is causing those files to be created improperly.

12-29-2012, 03:47 PM	#4
DeltaMac League Commissioner Join Date: Jan 2002 Posts: 7,948	Have you looked at that DU log before, since you have the Fusion drive? That log may be very normal for your configuration. I wonder if those (null) files are detritus from the changeover from a "downloading" file, to a "downloaded" file, that the file system doesn't quite deal with properly. Do those files show the same date (more or less)? Could be some weirdness in your system that just needs a restart.

12-29-2012, 03:52 PM	#5
benwiggy League Commissioner Join Date: Aug 2006 Posts: 5,039	Oh yes: I'm sure it's a normal log for the hardware: I've just never seen it before. I restart my Mac every morning: I'm sure it's just some random anomaly, I was just interested in its provenance. The two files have identical data and are one minute apart in creation date.

12-29-2012, 06:28 PM	#6
DeltaMac League Commissioner Join Date: Jan 2002 Posts: 7,948	Well, it sounds like it was connected with downloads that were successful at the time - even though there was some glitch, even something small like a short power interruption on your router (or maybe on the ISPs end), interfering briefly with your download, not enough to error out - but just long enough to leave you with a small mysterious "gift" If you have had normal downloads since that time, then just count it as a temporary wonder. As I think about it - maybe it's some small bug in the Fusion drive - the algorithm may still need some tweaking in a future ML system update for a Fusion drive that may be not quite 100% for all operations.